Skip to main content
Glama

Snapshot Registry

registry_snapshot
Read-onlyIdempotent

Read the registry summary: active objects and traits, loaded names, loader issues, etag and generatedAt. detail full includes definitions; names narrows them. includeInternal adds internal objects. Replies larger than 100,000 characters are refused with their size. object_registry reads one composed object; catalog_list reads components.

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

Input Schema

NameRequiredDescriptionDefault
namesNoExact trait and object names; misses go in notFound.
detailNosummary (default), or full definitions, best with names.summary
reproduceNoInclude the command and calls for reproducing this result.
includeInternalNoAlso list OODS Foundry's internal (non-business) objects, after the business objects. Without it they are left out and registry.hiddenInternal counts them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / names / items / description
      Added value: +"One trait or object name, such as Stateful or Subscription."
  2. Changed4 schema fields changed
    • removedInput schema / $id
      Removed value: -"https://designlab.local/schemas/registry.snapshot.input.json"
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / reproduce
      Added value: +{
      +  "default": false,
      +  "description": "Include the command and calls for reproducing this result.",
      +  "type": "boolean"
      +}
    • changedInput schema / title
      Previous value: -"registry.snapshot input"New value: +"registry_snapshot input"
  3. Changed3 schema fields changed
    • changedInput schema / description
      Previous value: -"Bulk-read recorded mappings plus live shipped and registered team traits and objects. Reports definition loader issues, including shadowed names. Draft preferred_terms, disambiguation_decisions and capabilities are not snapshot outputs."New value: +"Bulk-read recorded mappings plus live shipped and registered team traits and objects. Reports definition loader issues, including shadowed names. The default summary leaves out each trait's and object's schema, parameters, view extensions, semantics, tokens and metadata; detail full returns them, optionally only for named traits and objects. Draft preferred_terms, disambiguation_decisions and capabilities are not snapshot outputs."
    • addedInput schema / properties / detail
      Added value: +{
      +  "default": "summary",
      +  "description": "summary (default), or full definitions, best with names.",
      +  "enum": [
      +    "summary",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / names
      Added value: +{
      +  "description": "Exact trait and object names; misses go in notFound.",
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "minItems": 1,
      +  "type": "array",
      +  "uniqueItems": true
      +}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds real behavior beyond that: oversized replies above 100,000 characters are refused with their size, and loader issues including shadowed names are reported. It does not describe what a refusal error looks like or pagination behavior, which keeps it below a 5.

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?

Extremely dense and front-loaded: the primary payload comes first, then parameter effects, then the size guardrail, then sibling routing. Every clause carries information, though the telegraphic style and jargon like 'loaded names' and 'active objects' cost some readability.

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?

There is no output schema, so the description must carry the return shape, and it only sketches top-level keys without field types or the shape of loader issues and notFound. It covers the critical edge case (size refusal) and the includeInternal hiding rule, but a caller cannot fully predict the response structure from this text.

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 coverage is 100%, so the schema already defines every parameter; baseline would be 3. The description earns extra by explaining the interaction between parameters ('detail full includes definitions; names narrows them') and the hiddenInternal count effect of includeInternal, which the per-field schema text does not make explicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Read the registry summary') and enumerates the payload (active objects and traits, loaded names, loader issues, etag, generatedAt). It also explicitly contrasts itself with the two sibling readers, so an agent can distinguish it without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names both alternatives and what they do ('object_registry reads one composed object; catalog_list reads components'), which routes an agent away from this tool when it wants a single object or a component list. It stops short of an explicit 'use this when X, not when Y' statement, so the routing is inferential rather than spelled out.

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.