Skip to main content
Glama
Sign In

Nothing.gripe

by io.github.AmithKumar1
OverviewDiscussionsAdmin

estimate_price

Ask the SENTIQ oracle what a task should cost and how long it takes before you post it.

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": {
      "text": "<text>"
    },
    "name": "estimate_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe task in plain words, at least a sentence.
amountNo
currencyNoISO code, e.g. INR, USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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 disclosure. It says the tool consults an oracle for cost and duration, but does not state whether it is read-only, whether it uses external services, what permissions are needed, or any side effects.

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

Conciseness5/5

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

The description is a single front-loaded sentence that states what the tool does and when to call it, with no redundant or wasted phrasing.

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 simple three-parameter tool with no output schema or annotations, the description conveys the core action and a usage hint. However, it leaves unclear how amount and currency affect the estimate, and it does not explain the estimation output beyond cost and time.

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 description coverage is 67%, and the 'amount' parameter has no description anywhere. The description adds no guidance on what 'amount' or 'currency' mean in the context of an estimation call, so it does not compensate for the undocumented parameter.

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 states a specific verb ('Ask...what a task should cost and how long it takes') and resource (task price and duration), so an agent can tell what the tool returns. It implicitly distinguishes itself from post_task by saying 'before you post it,' but it never names that sibling explicitly, 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 Guidelines4/5

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

The phrase 'before you post it' gives clear timing context: use this tool prior to posting a task. It does not name alternatives or state exclusions, so it falls short of the explicit when/when-not routing of a 5.

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

All Nothing.gripe toolsInspect
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