Skip to main content
Glama

get_formalisation

Read-only

One declaration in full: its sources, related formalisations, main results, the results held here it joins and on what key, Palomar's registrations of it, and any contradiction between what it declares and what a rebuild found.

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": {
      "id": "<id>"
    },
    "name": "get_formalisation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesowner/repo for a root declaration, owner/repo/path, or its GitHub URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description goes further by disclosing the shape of the response — that it joins results on a key, includes Palomar registrations, and reports any contradiction between the declaration and a rebuild — which is meaningful behavioral context for a read tool with no output schema.

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 sentence, front-loaded with the core idea ('One declaration in full') followed by a compact enumeration of what the payload contains. Every clause carries information; the only mild cost is the dense comma-list style.

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?

With no output schema and only one parameter, the description carries the burden of describing return contents, and it does so thoroughly, including the contradiction signal that an agent would not otherwise anticipate. It stops short of covering failure modes, e.g. an id that resolves to nothing or is ambiguous.

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 coverage is 100% and the id parameter already documents all three accepted forms (owner/repo, owner/repo/path, GitHub URL). The description adds nothing about identifier format, resolution rules, or what happens on a non-root path, so the baseline 3 applies.

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 and scope — a single declaration retrieved in full, with an enumerated payload (sources, related formalisations, main results, registrations, contradiction flags). This clearly separates it from list/search siblings like search_formalisations and from get_statement, though the verb is implied rather than stated ('One declaration in full').

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: an agent can infer this is the drill-down call once it has an identifier from a search or listing tool. There is no explicit when-to-use statement, no mention of prerequisites such as needing a known id, and no named alternative for fetching partial data.

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