Skip to main content
Glama

Matchmaking rating for agent selection

query_rating

Pre-delegation query $0.01 (trial applies)

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

Input Schema

NameRequiredDescriptionDefault
agentNo
dimensionNo
task_ratingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / task_rating
      Added value: +{
      +  "type": "number"
      +}
  2. First observed

TDQS

D1.8/5.0
Behavior2/5

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

No annotations exist, so the description carries full behavioral burden. It does disclose a cost ($0.01) and a trial condition, which is genuine behavioral context, but it says nothing about read-only semantics, auth requirements, or what a query returns.

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

Conciseness2/5

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

It is short, but brevity here is under-specification rather than efficiency — a five-word fragment plus a parenthetical pricing note. Nothing about purpose is front-loaded because purpose is never stated.

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

Completeness1/5

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

A three-parameter tool with no annotations, no output schema, and no documented parameters needs a full description; this provides none of it. Pricing alone does not let an agent invoke the tool correctly.

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

Parameters1/5

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

Three parameters (agent, dimension, task_rating) with 0% schema description coverage and no meaning added in the description. The text does not mention any parameter at all, leaving every input undefined.

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

Purpose2/5

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

The phrase 'Pre-delegation query' restates the name's 'query' without identifying the resource or what is being rated — it never says it queries agent ratings or task ratings. The only concrete content is a price, which does not tell an agent what the tool does.

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?

'Pre-delegation' vaguely implies timing (call before delegating), but no alternative is named and neither ingest_receipt nor rank_agents is referenced. An agent cannot tell from this text why it would pick query_rating over rank_agents.

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