Skip to main content
Glama

List frameworks

list_frameworks
Read-onlyIdempotent

List bundled framework IDs, coverage, source lineage, version, and the framework-pack digest.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is fully covered. The description adds nothing beyond that on ordering, whether results are cached/static, or how the 'digest' should be interpreted, and its enumeration of returned fields largely duplicates what the output schema can carry.

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 the verb and resource first, then the returned attributes. No filler, no restatement of the title beyond the necessary verb+noun, and every phrase carries information.

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 zero-parameter read tool with an output schema present, the description is nearly sufficient: it tells the agent what categories of data come back without needing to re-explain return values. Minor gap is that the ordering and whether the digest is per-pack or aggregate is left undefined, but that is marginal given the output schema.

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 zero parameters, so the baseline is 4 — there is no parameter meaning for the description to supply. The description is not misleading about inputs and implicitly confirms the no-argument nature by promising an unfiltered listing.

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 ('List') and resource ('frameworks') and enumerates the fields covered (IDs, coverage, source lineage, version, digest), which makes the scope clear against the singular get_framework sibling. It stops short of explicitly naming that differentiation, so it is clear but not sibling-aware.

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?

Discovery usage is implied by 'List bundled framework IDs' — an agent can infer this is the entry point before calling get_framework or compile_disclosure. However, no when-to-use condition, prerequisite, or named alternative is provided, leaving the choice between siblings to inference.

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.