Open-End Response Analyser – coding of open-ended survey answers

Get Open-End pricing

open_end_get_pricing

Read-onlyIdempotent

Returns the credit price list (1 credit = 1 valid response, charged once per project) and, with 'responses', how many credits an analysis of that many responses costs and the smallest sufficient credit package. Use it for price questions like 'how much does it cost to analyse 3000 answers'. No account needed. Does not check the user's balance; use open_end_estimate_analysis for an existing project.

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": "open_end_get_pricing"
  }
}

Input Schema

Name	Required	Description	Default
`responses`	No	Number of responses to price (optional).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description adds behavior they cannot express: no authentication is required, the tool does not read the user's balance, and the credit charging model. These are exactly the non-obvious facts an agent needs before deciding how to answer a pricing question.

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?

Front-loaded with the primary return value and tightly packed; every clause carries information (unit pricing, optional pricing mode, no-auth, sibling boundary). The second clause is slightly convoluted in its nesting ('with responses, how many credits an analysis of that many responses costs'), which costs it a point.

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

Completeness5/5

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

For a single-optional-parameter, read-only tool with no output schema, the definition covers what it returns, the units, the auth requirement, the conditional mode, and the sibling boundary. There is nothing an agent needs in order to call it or interpret its result that is left unstated.

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 'responses' is already documented as an optional response count. The description goes beyond that by explaining the consequence of supplying it (cost of analysing that many responses plus the smallest sufficient credit package), which the schema does not state. It stops short of noting the upper bound, so not a 5.

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?

States a specific verb+resource ('Returns the credit price list'), defines the unit semantics (1 credit = 1 valid response, charged once per project), and differentiates from the sibling by declaring what it does not do (no balance check). An agent can distinguish it from open_end_estimate_analysis without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use with a concrete example ('price questions like how much does it cost to analyse 3000 answers') and an explicit routing rule away from it ('use open_end_estimate_analysis for an existing project'). Both the positive and negative cases are covered.

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

All Open-End Response Analyser – coding of open-ended survey answers tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?