Skip to main content
Glama

search_formalisations

Read-only

Every formalization.yaml the register has read, with what each declares about its own axioms, unproved goals, assumed literature, automation and review, and who has checked it: this register, Palomar, or nobody independent of its authors.

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

Input Schema

NameRequiredDescriptionDefault
flagNo
limitNo
queryNoText to match in name, repository, path, authors or models
methodNo
reviewNo
held_onlyNoOnly declarations joined to a result held here
checked_byNoWho checked it; none for declarations nobody independent has checked

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe read, and the description adds real context beyond that: it discloses that the corpus is everything the register has read and that each record carries self-declared claims plus an independence-of-checker dimension. It does not mention pagination behavior, the default limit of 25, or how incomplete declarations are represented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no waste, but the colon-delimited clause chain makes it dense and hard to scan. The core fact — this is the register-wide formalization listing — is front-loaded, which helps.

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 seven-parameter tool with no output schema and 43% schema coverage, the description covers the conceptual model (declarations plus checker provenance) but leaves the filtering mechanics — query, limit, method, held_only — undocumented anywhere. Adequate orientation, incomplete invocation detail.

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 only 43%, so the description carries partial burden. It usefully glosses the provenance axis ('this register, Palomar, or nobody independent of its authors') which clarifies the checked_by enum's 'none' value, and its list of declared facets maps onto the flag values. It says nothing about query, limit, method, or held_only, leaving half the surface to the schema alone.

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 the resource precisely — every formalization.yaml the register has read — and enumerates what each entry carries (axioms, unproved goals, literature, automation, review, checker provenance). That is enough for an agent to know this is a bulk declaration listing, though it never states a verb like 'search' or 'filter' and does not distinguish itself from get_formalisation or search_statements.

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 when-to-use guidance, no statement of when to prefer get_formalisation or search_statements, and no exclusions. The agent must infer from the tool name and parameters that this is the broad listing tool.

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.

Resources