Skip to main content
Glama

get_openapi_spec

Retrieve the raw OpenAPI 3.1 specification for the Physicist API to inspect endpoints, schemas, and request details for integration or validation.

Instructions

Retrieve the raw OpenAPI 3.1 specification for the Physicist API.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full disclosure burden. It does add genuine behavioral signal by specifying the document is "raw" and conformant to OpenAPI 3.1, which tells the agent not to expect a summarized or transformed view. It does not say whether the payload is JSON or YAML, how large it may be, or whether it is cached/stable across calls.

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

Conciseness5/5

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

A single front-loaded sentence with no filler. Every phrase ("raw", "OpenAPI 3.1", "Physicist API") carries information an agent would otherwise have to guess.

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 simple zero-argument read tool with no output schema, the definition covers what the tool is and which document it returns. The only meaningful omission is the serialization format and rough size of the returned specification, which matters slightly since the agent must parse it.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies the call is unconditional and argument-free.

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?

A specific verb ("Retrieve") plus a specific resource ("raw OpenAPI 3.1 specification for the Physicist API"), including the version and the fact that it is raw rather than summarized. No sibling tool in the list returns a specification document, so the tool is distinguishable in practice, though the description never says so explicitly.

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?

The use case is implied: call this when you need the API contract itself. There is no explicit when-to-use framing, no statement about when a computed/derived alternative would be preferable, and no prerequisites (auth, availability). For a zero-parameter fetch tool the implied guidance is largely sufficient, but it is not spelled out.

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