Skip to main content
Glama

get_schema

Read-only

Return the strict JSON Schema, limits, rules, and examples for a resume, cover letter, or profile. Call this before drafting that document.

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": {
      "document": "<document>"
    },
    "name": "get_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful context by naming the return payload (schema, limits, rules, examples), which matters because there is no output schema. It says nothing about caching, freshness, or whether limits vary per document type.

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?

Two short sentences, front-loaded with what is returned and followed immediately by the call-timing instruction. No filler or redundant restatement of the title.

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 single-parameter read-only lookup with no output schema, the definition covers what comes back and when to call it, which is sufficient to invoke correctly. The only meaningful gap is the unresolved relationship with get_guidelines, which also appears to expose rules.

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 0%, so the burden falls on the description, and it only restates the three enum values (resume, cover letter, profile) without explaining what distinguishes them or what each schema contains. It does at least confirm the parameter is a document-type selector, but adds no meaning beyond the enum already present in the schema.

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?

States a specific verb and resource: returns the strict JSON Schema, limits, rules, and examples for one of three document types. This is clearly distinguishable from get_resume/get_cover_letter/get_profile, which return actual documents. It does not, however, distinguish itself from the sibling get_guidelines, which plausibly also returns rules and limits.

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?

"Call this before drafting that document" gives explicit sequencing guidance that tells the agent exactly when in the workflow to invoke it. There is no statement of when not to call it, nor any routing note versus get_guidelines, so it falls short of full when/when-not/alternative coverage.

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