Skip to main content
Glama

rank_sources

Idempotent

Ranks candidate data sources for a concept using composite scores, returning best-first results so agents can choose where to fetch the required data.

Instructions

Rank candidate sources for a concept (best-first) with composite scores.

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": {
      "concept_id": "<concept_id>"
    },
    "name": "rank_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
concept_idYes
requested_dateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already establish idempotence, non-destructiveness, closed-world scope, and that this is not a read-only operation. The description adds useful behavior ('best-first' ordering and 'composite scores'), but does not explain why the tool is not read-only or what side effects, if any, the ranking produces.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately terse, though the terseness contributes to missing semantics elsewhere.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but with two parameters at 0% schema description coverage the description should clarify concept_id and requested_date and the non-read-only behavior. It leaves too much for the agent to infer.

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 0%, so the description must carry parameter meaning, but it only references 'concept' implicitly and says nothing about the required concept_id or the optional requested_date. The function of requested_date is entirely undocumented.

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 (rank) and resource (candidate sources) and adds the scoping concept and ordering ('best-first' with composite scores). It is clear what the tool does, though it does not distinguish itself from any sibling.

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 guidance on when to use this tool versus alternatives or when not to use it. The ranking purpose implies its use, but no conditions or prerequisites are given.

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