Skip to main content
Glama

Submit by Hand

Plans and prices

get_pricing
Read-only

Plans for having our team submit the product to directories by hand: price, number of directories, delivery window, what is included, refund terms, and what the same directories take when done by hand. One-time payment, no subscription.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine business context beyond that: one-time payment with no subscription, and a comparison against manual submission costs. However, it says nothing about whether prices are static or per-region, whether plans expire, or how the manual comparison figure is derived.

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?

Two sentences, no filler, with the field list and the payment-model note separated cleanly. The first sentence is a dense comma chain that takes effort to parse, but every clause carries information about the returned data.

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?

With no input schema fields and no output schema, the description carries the burden of describing the return payload, and it does so by enumerating the plan attributes. What remains unstated is secondary: currency, whether plans are region-specific, and ordering of results.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing inputs and instead spends its words on what comes back.

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?

The description names a specific resource (directory-submission plans) and enumerates the fields each plan carries: price, number of directories, delivery window, inclusions, refund terms, plus a manual-comparison figure. An agent can tell this is the pricing-catalog read, distinct from create_order or get_directory. The phrasing 'Plans for having our team submit the product to directories by hand' is convoluted and momentarily reads as if the agent does the submitting, which keeps it from a 5.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of the sibling tools (create_order, get_order_status) that would naturally follow a pricing lookup. The only implied usage is that this is a pre-purchase reference, which the agent must infer from the presence of prices and refund terms.

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