roastify_set_pricing_modelSet the active pricing model. RESTRICTED to operator.
Requires a valid proof (Schnorr-signed kind-27235 event) proving the caller holds the operator's nsec.
| Name | Required | Description | Default |
|---|---|---|---|
| dpop_token | No | ||
| model_json | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses an operator-only restriction and requires a Schnorr-signed kind-27235 proof that the caller holds the operator's nsec. This is meaningful behavioral context, though it does not describe side effects or failure behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded: the core action appears first, followed by the access restriction and proof requirement. Every sentence earns its place, and there is no redundant filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The authentication precondition is well covered, but the required model_json parameter is left undefined at 0% schema coverage. An agent would not know what to put inside model_json or how the pricing model should be represented. This incompleteness makes the tool hard to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain either parameter. model_json is required but its expected format, structure, and meaning are completely unspecified. dpop_token is also undocumented, leaving the agent without enough information to construct a correct call.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: 'Set the active pricing model.' It uses a specific verb and resource, and it is distinguishable from read operations like roastify_get_pricing_model. However, it does not explicitly distinguish itself from roastify_reset_pricing_model, so some sibling differentiation is missing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides an access restriction ('RESTRICTED to operator') but gives no guidance on when to choose this tool over alternatives such as roastify_reset_pricing_model or roastify_get_pricing_model. There is no conditional context, no exclusions, and no mention of when this should or should not be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.