Skip to main content
Glama

research_sources

Lists platforms that can be researched via public, key-free, read-only endpoints and explains why blocked sources are unavailable, helping agents pick valid sources without silent substitution.

Instructions

Which platforms the body can actually research, and which are blocked.

Every readable source is a public, documented, key-free endpoint (read-only, rate-limited, no login). Blocked ones say why - no silent substitution.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description discloses important traits: readable sources are public, documented, key-free, read-only, rate-limited, and require no login; blocked sources include reasons without silent substitution. It does not describe output shape or whether this call performs live checks, but it provides substantial safety and access context.

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 two-sentence structure front-loads the readable/blocked distinction, then adds the access properties. The opening fragment 'Which platforms...' is slightly awkward, but there is no wasted wording overall.

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

Completeness4/5

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

For a no-parameter, no-output-schema discovery tool, the description gives enough context about what is classified and why blocked entries are included. It does not specify return structure, but the complexity is low and the key behavioral conditions are covered.

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?

There are zero parameters, so there is no parameter meaning to add beyond the empty schema. The baseline for a no-parameter tool applies.

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 identifies the resource as the set of researchable versus blocked platforms, and the second sentence clarifies the readable-source properties. It does not use a clear verb such as 'list' or 'returns,' and it does not name a sibling, but the scope is still discernible.

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?

No explicit when-to-use guidance or alternative tools are named. An agent can infer it is a discovery/status tool to consult before calling research_source or research_any, but that inference is not stated.

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