Skip to main content
Glama

Get framework

get_framework
Read-onlyIdempotent

Return one bundled framework's required datapoints, mappings, sources, and framework-pack lineage.

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": {
      "framework": "<framework>"
    },
    "name": "get_framework"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkYesFramework id, for example esrs-e1 or ca-sb253; see list_frameworks.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / framework / description
      Added value: +"Framework id, for example esrs-e1 or ca-sb253; see list_frameworks."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only that the result is the bundled content plus lineage, without saying what happens for an unknown framework id or how large the payload may be.

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?

One tight sentence with the verb front-loaded and no filler; every noun maps to returned content. It is slightly list-heavy and could route the agent to alternatives, but nothing is wasted.

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 tool with an output schema and full annotation coverage, the return contents are adequately framed, so return-value explanation is unnecessary. The only meaningful gap is the absent when-to-use routing, which is scored separately.

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 100% and the single parameter already documents the id format with examples and points at list_frameworks for discovery. The description adds no meaning beyond that, so the baseline of 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 names a specific verb (Return) and resource (one bundled framework) and enumerates the payload: required datapoints, mappings, sources, and framework-pack lineage. The word 'one' implicitly contrasts with the list-style sibling, though it does not name list_frameworks explicitly.

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

Usage Guidelines2/5

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

There is no explicit statement of when to call this versus list_frameworks or compile_disclosure; the only routing hint ('see list_frameworks') lives in the schema's parameter description, not the tool description. An agent must infer that this is the detail-fetch counterpart to the list operation.

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.