Skip to main content
Glama
Sign In

concordance

by com.narrowhighway
OverviewDiscussionsAdmin

timeline

[WORD · internal] Timeline — Old Testament, New Testament (Acts onward), and Church History, one spine from creation to today. Genuinely disputed dates (early/late Exodus, the date of Revelation, etc.) carry both positions, never one verdict. Pass id for one event; else lists every event grouped by era and period.

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

Input Schema

NameRequiredDescriptionDefault
idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / id / maxLength
      Added value: +4000
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that disputed dates carry both positions rather than a single verdict, and that results are grouped by era and period, but says nothing about auth requirements, read-only nature, or the shape/limits of the returned list.

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?

Three tight sentences with no filler, and the scope is front-loaded before the parameter behavior. The leading '[WORD · internal]' tag is cryptic but consumes minimal space.

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 simple tool with one optional string parameter, no nested objects, and no output schema, the description covers purpose, behavioral quirks, and parameter branching adequately. The main gap is the absence of return-format or permission detail, which is minor at this complexity.

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?

Schema description coverage is 0% and the single 'id' parameter is undocumented in the schema, so the description must compensate. It does so by explaining that passing id returns one event while omitting it lists all events, which is the essential semantic distinction; it stops short of describing the id format.

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 resource (a single timeline spine spanning Old Testament, New Testament from Acts onward, and Church History) and its scope from creation to today, which is clear enough to identify the tool. It does not, however, explicitly differentiate itself from related siblings such as harmony, narratives, or prophecy_traces, so an agent must infer the boundary.

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?

It gives conditional usage of the parameter ('Pass id for one event; else lists every event'), which tells the agent how to branch, but offers no guidance on when to prefer this tool over sibling resources. Usage is implied by the input shape rather than stated as when/when-not guidance.

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

All concordance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources