Skip to main content
Glama

roastify-mcp

by io.github.lonniev

Roastify Request Adoption

roastify_request_adoption

Ask a chosen Authority to adopt this operator (deferred courtship).

RESTRICTED to the operator — requires proof the caller controls this operator's npub. Resolves the Authority's MCP endpoint from the community registry, mints an inline ownership proof with this operator's nsec, and delivers the request MCP-to-MCP. The Authority records it as pending; its owner approves on their own time. Poll adoption_status for progress; the operator flips to ready once the Authority provisions it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNooptional message for the Authority owner.
dpop_tokenNooperator-npub ownership proof (inline kind-27235 or cached token).
service_urlNothis operator's MCP endpoint (advertised to the Authority).
authority_npubYesnpub of the Authority to request adoption from.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it delivers: it discloses that the tool resolves an Authority endpoint, mints an inline proof using the operator's nsec, delivers MCP-to-MCP, records the request as pending, and requires ownership proof. This gives the agent a clear model of side effects and security-sensitive behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The primary purpose is front-loaded and the rest is dense, valuable process detail with almost no filler. The parenthetical 'deferred courtship' and the long second sentence add a bit of color/compressness but do not seriously hurt scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, return values need no explanation, and the description covers what happens before, during, and after the call: restriction, proof, endpoint resolution, pending state, and polling adoption_status until ready. Minor ambiguity around whether the caller supplies or the tool mints the ownership proof keeps this from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds operational meaning beyond the field descriptions: it explains why authority_npub is sufficient (endpoint resolved from community registry), ties dpop_token to the ownership-proof requirement, and clarifies service_url's role in MCP-to-MCP delivery. It does not explicitly name each parameter but supplements the schema usefully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Ask a chosen Authority to adopt this operator.' It also distinguishes itself from the status-checking sibling by directing the agent to 'Poll adoption_status for progress,' making the request vs. status role unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the intended use (requesting adoption), explicitly restricts the tool to the operator, and points to adoption_status as the follow-up for progress. It does not enumerate exhaustive when-not-to-use conditions, but the restriction plus the alternative is enough practical guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All roastify-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools target clearly distinct resources—patron balances vs. operator Authority balances, design text vs. full design fetches, operator vs. patron credentials—and the verbose descriptions carefully separate request/receive flows. A few pairs could still be confused at a glance, such as service_status/session_status, forget_coupon/delete_coupon, and get_design_text/fetch_design.

Naming Consistency4/5

All tools share the roastify_ snake_case prefix and mostly follow a verb_noun pattern like list_, get_, update_, delete_, and create. However, several noun-only names (service_status, session_status, account_statement, oracle_about) and the inconsistent forget_ vs. delete_ distinction for credential/coupon removal keep it from being fully consistent.

Tool Count1/5

69 tools is an extreme count for a single MCP surface and far exceeds the 25+ threshold. Even though the tools span many subdomains—design, payments, coupons, credentials, pricing, notarization, oracle—the sheer number will be heavy on agent context and selection accuracy.

Completeness3/5

Core workflows are largely covered: design storage/editing, coupon lifecycle, credential vaults, credit purchasing, pricing models, notarization, and the oracle all have reasonable read/write surfaces. However, session_status explicitly tells not_registered operators to call register_operator, which does not exist in the tool set, and design editing lacks any delete-element operation, leaving notable dead ends.

Resources