Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_schema_get

Read-onlyIdempotent

Retrieve compact TypeScript-like field declarations for API request and response schemas from an OpenAPI contract by schema name, tool name, operationId, or keyword query.

Instructions

Get the fields of API request and response schemas as compact TypeScript-like declarations from the OpenAPI contract: type, required or optional, enum values and a one-line description per field. Pass schema names (e.g. "CreateInvoiceRequest"), or a tool name or operationId (e.g. "beel_create_invoice") for its query, body and return type. Schemas a declaration references are named, not expanded; query lists names.

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

Input Schema

NameRequiredDescriptionDefault
nameNoA schema name, a tool name or an operationId.
namesNoSeveral in one call (at most 10), e.g. ["Recipient", "TaxInfo"].
queryNoLists the schema names that contain it, ignoring case, e.g. "invoice".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add real behavior: it discloses the output format, that referenced schemas are 'named, not expanded', and that query mode returns names rather than declarations. These are non-obvious traits an agent needs; only the lack of any note on output size or truncation keeps it from 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?

Three sentences, front-loaded with what is returned, then input modes, then the reference/expansion caveat; the parenthetical examples earn their space. The closing clause 'query lists names' is telegraphic enough that it reads slightly ambiguously, which is the only real cost.

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 three-optional-parameter, non-destructive introspection tool with no output schema, the description covers the return shape, the three lookup modes, and reference non-expansion. It stops short of saying how large a declaration can be or whether the response is capped, which would help an agent plan follow-up calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description genuinely adds meaning: `name` accepts three identifier kinds and the description explains what each yields (query, body and return type for a tool name), with examples like "CreateInvoiceRequest" and "beel_create_invoice". It also clarifies that query mode's result is a name list, which is a semantic distinction the schema text alone leaves ambiguous.

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?

States a specific verb and resource: 'Get the fields of API request and response schemas ... from the OpenAPI contract', and pins the output form ('compact TypeScript-like declarations'). It is clearly distinguishable from the docs tools (beel_docs_get/beel_docs_search) and from every CRUD sibling, since none of them introspect the contract.

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?

Gives concrete selection rules for each input mode: pass schema names for a type, or a tool name/operationId for 'its query, body and return type', or use query to discover names. That is clear when-to-use context with worked examples, but it never names an alternative (e.g. beel_docs_get) or states when this tool is the wrong choice.

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

Deploy Server

Other Tools