Skip to main content
Glama

Confirm price on request

confirm_price_on_request
Destructive

Confirm that an imported activity is priced on request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "activity_id": "<activity_id>"
    },
    "name": "confirm_price_on_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, so the agent already knows this mutates state. The description adds nothing about what is overwritten, whether an existing price is discarded, whether the action is idempotent, or what permissions are required — the most important behavioral facts for a destructive call. The benign verb 'confirm' arguably understates the destructive flag rather than clarifying it.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though that efficiency is partly achieved by omitting information the agent needs.

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

Completeness3/5

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

For a two-parameter mutation with no output schema and only one documented parameter, the description should at minimum state the effect of the call. Safety annotations cover the risk profile, but the absence of any stated outcome or parameter constraint leaves the definition thin relative to the destructive operation it exposes.

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

Parameters2/5

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

Schema coverage is 50%: business_id is documented in the schema but activity_id has no description. The description only implicitly ties the operation to an activity identifier and does not state that it must reference an imported activity, nor does it say anything about the business scoping of the call. It therefore does not compensate for the coverage gap.

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

Purpose4/5

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

Names a specific verb (confirm) and a specific resource state (an imported activity priced on request), which distinguishes it from generic update tools in the sibling list. The remaining ambiguity is operational: it is unclear whether 'confirm' writes a price-on-request flag or verifies an existing one, and the phrase 'imported activity' leaves the precondition implicit.

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

Usage Guidelines2/5

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

Gives no when-to-use or when-not-to-use guidance, no prerequisites beyond the embedded word 'imported', and names no alternative tool. An agent cannot tell from this sentence whether it should call this before or after create_activity/import_website, or whether it is safe to call repeatedly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources