Skip to main content
Glama

AI Site Scorer

get_signal

Get one registry signal card: evidence level, sources with dates, how it is measured, fix template. Free, no auth.

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": {
      "signal_id": "<signal_id>"
    },
    "name": "get_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
signal_idYese.g. access.search_bots_robots

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two valuable traits beyond the schema — that the call is free and requires no auth — and it describes what the returned card contains. However, it says nothing about failure behavior for an unknown signal_id, rate limits, or whether the card is static versus freshly computed.

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 dense sentence with the payload contents front-loaded and no filler; the 'Free, no auth' clause is placed at the end as a secondary qualifier. The compressed noun list is slightly cryptic but every clause earns its place.

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 one-parameter read tool with no output schema, the description should explain return shape, and it partially does via the field list. Still missing is how a signal card relates to the broader workflow (list_signals to discover ids, get_fix_plan to act on the fix template) and what an invalid id yields.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter already carries a concrete example ('access.search_bots_robots'), so the schema does the heavy lifting. The description adds only that the id refers to a registry signal card, which is marginal meaning beyond structured data. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Get one registry signal card') and enumerates the card's contents (evidence level, dated sources, measurement, fix template), which tells the agent exactly what it retrieves. It implicitly contrasts with list_signals ('one' vs a list), but never names a sibling explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: 'Get one ... card' suggests fetching details for a known signal id, while list_signals would be the discovery path. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as list_signals or get_fix_plan. 'Free, no auth' is a useful precondition but is not selection guidance.

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