Skip to main content
Glama

context_sources

Reports available local data sources and confirms read-only access boundaries without exposing file paths or content.

Instructions

Describe source availability and the read-only boundary without exposing paths or contents.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two genuine behavioral traits an agent could not otherwise know: the operation is read-only and it deliberately withholds paths and contents. It stops short of saying what the response actually contains, whether availability can be partial or error out, or how to act on a negative result.

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?

A single clause with zero filler, front-loading the operation ('Describe source availability') and then the key constraint ('without exposing paths or contents'). Nothing could be removed without losing information.

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 zero-parameter tool with no output schema, the description should compensate by explaining what the call returns, since nothing else does. It establishes the read-only, no-paths, no-contents boundary but leaves the shape of the answer (a list of source names? availability flags?) unspecified, so the agent knows the constraints but not the payoff.

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?

The tool takes zero parameters and the schema is an empty object, so there is no parameter meaning to add. Baseline 4 applies; the description correctly says nothing about inputs.

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

Purpose3/5

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

The verb 'describe' and the object 'source availability' give a rough sense of purpose, and the read-only boundary clause hints this is a metadata/discovery call rather than a content fetch, which distinguishes it from siblings like context_read_session and context_search. However, 'source' is never defined, so an agent cannot tell what a source is or what the description actually reports back.

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 when-to-use statement and no named alternative. The only implicit signal is that, because contents and paths are withheld, this is a reconnaissance call to run before reading; the agent has to infer that ordering itself, and no exclusion tells it when this tool is the wrong choice versus context_recent or context_search.

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