Skip to main content
Glama

SophiaLabs & Nomos Open-Core MCP

search_nomos_corpus

Read-onlyIdempotent

Search Nomos Handbook chapters, Empirical Dispatches, Open-Core Architecture Specs, CLI reference, and comparison tables.

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": {
      "query": "<query>"
    },
    "name": "search_nomos_corpus"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch keywords or technical problem terms
sectionNoOptional corpus subset filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing behavioral on top of that — no indication of how results are ranked, whether matching is keyword or semantic, whether results are truncated, or what a hit looks like.

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; every listed corpus carries real scope information. The only mild cost is that the enumeration reads as a list rather than a statement of intent, but nothing is wasted.

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 two-parameter read-only search with no output schema, the description covers scope adequately, and annotations handle safety. It stops short of telling an agent how to act on results or how this search relates to the sibling analysis tools, which leaves a real gap for a retrieval tool feeding a multi-step workflow.

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?

Schema description coverage is 100%, with both the query string and the section enum fully documented in the schema, so the baseline of 3 applies. The description adds no extra meaning about query syntax, multi-term handling, or how the section filter interacts with the enumerated corpora.

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 gives a specific verb ("Search") tied to a named resource (the Nomos corpus) and enumerates the concrete subsets covered: handbook chapters, dispatches, specs, CLI reference, comparison tables. That enumeration distinguishes it from the sibling tools, which are all analysis/advisory rather than retrieval, though the description never explicitly names those siblings.

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?

Usage is only implied through the corpus enumeration: an agent can infer this is the retrieval entry point for Nomos material. There is no explicit statement of when to prefer this over compare_governance_approaches or recommend_adoption_plan, and no prerequisites or exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.