Skip to main content
Glama
Sign In
Context Layer Lab

Context Layer Lab

by Kaagemusha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

explain_source

Read-onlyIdempotent

Reveal a declared source and the exact claims it supports on one governed context record, so you can verify which evidence backs an operational answer.

Instructions

Show a declared source and the exact claims it supports on one context record.

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": {
      "recordId": "<recordId>",
      "sourceId": "<sourceId>"
    },
    "name": "explain_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordIdYes
sourceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that output is a source plus the claims it supports on one record, which is useful framing, but says nothing about result format, emptiness cases, or whether the source must already be declared.

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, front-loaded sentence with no filler. It is efficient, though its brevity is part of why parameter and usage detail is missing.

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 read-only lookup tool with no output schema, the description covers the conceptual output but omits parameter meaning and usage routing. Adequate at a minimum-viable level, but leaves real gaps an agent would face when invoking it.

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% for both required parameters. The description only obliquely implies the mapping ('one context record' -> recordId, 'declared source' -> sourceId) without explaining ID format, scope, or whether the source must pre-exist. It fails to compensate for the coverage gap.

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 ('Show') and resource ('a declared source and the exact claims it supports'), so an agent can tell it produces a source-to-claims view. However, it does not distinguish itself from siblings like search_context or validate_record, leaving the boundary to inference.

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 guidance is given on when to use this tool versus search_context, validate_record, or inspect_ingestion. The agent must guess the triggering scenario from the description alone.

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

Deploy Server

Other Tools