Skip to main content
Glama
Sign In

concordance

by com.narrowhighway
OverviewDiscussionsAdmin

word_study

[WORD · door] Strong's word study — original-language definition + pronunciation + every occurrence.

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": {
      "strongs": "<strongs>"
    },
    "name": "word_study"
  }
}

Input Schema

NameRequiredDescriptionDefault
strongsYese.g. G26, H2617

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the return content (definition, pronunciation, every occurrence), which implies a read-only lookup, but it says nothing about result size limits, pagination, or whether occurrences are capped, which matters for a tool promising 'every occurrence'.

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 compact line with the core purpose front-loaded after a short tag. The '[WORD · door]' prefix is somewhat cryptic but consumes little space, and no sentence is wasted.

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 one-parameter lookup with no output schema and no annotations, the description adequately states the three things returned (definition, pronunciation, occurrences). It is close to complete; only edge-case behavior such as missing Strong's numbers or occurrence limits is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter with 100% schema description coverage, including the example format 'G26, H2617'. The description adds no syntax or format detail beyond the schema, so the schema does the heavy lifting and the baseline of 3 is appropriate.

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 names a specific verb+resource: a Strong's word study returning the original-language definition, pronunciation, and every occurrence. That is concrete and distinguishable from generic siblings like lookup or search. It does not, however, clarify how it differs from close siblings such as original_words, pronounce, or define, which appear to overlap.

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 like original_words, pronounce, thesaurus, or define, despite several apparently overlapping siblings. Usage is only weakly implied by the phrase 'Strong's word study'.

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