Skip to main content
Glama

STATIC

STATIC page section

static_get_section
Read-onlyIdempotent

Returns one section of the STATIC product page, such as key features, editions, use cases or industry standards. Use a title from static_list_sections.

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": {
      "section": "<section>"
    },
    "name": "static_get_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection title or anchor, e.g. "Key features".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.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 and idempotency profile is covered. The description adds that a single section is returned and implies titles must be valid, but it does not say what happens with an unknown section or what the response contains. Useful but modest value on top of rich annotations.

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 tight sentences with zero filler: the return value and scope come first, followed by the actionable constraint on the input. Every clause earns its place.

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 one-parameter read tool with full schema coverage, rich annotations, and no output schema, the description supplies everything needed to call it correctly. The only omissions are error behavior for an invalid title and the exact shape of the returned section, both minor here.

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?

Schema coverage is 100% and the single parameter is already documented with an example, so the baseline is 3. The description goes further by naming the authoritative source of valid values (static_list_sections) and listing likely section titles, which meaningfully constrains what to pass and reduces trial-and-error.

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?

The description states a specific verb and resource ("Returns one section of the STATIC product page") and enumerates concrete section examples (key features, editions, use cases, industry standards), which lets an agent distinguish it from siblings like static_list_sections and static_overview without opening any schema.

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?

"Use a title from static_list_sections" gives an explicit prerequisite and names the exact tool that supplies valid input, which is strong workflow guidance. It stops short of saying when to prefer this tool over static_overview or other siblings, so it is clear context rather than a full when/when-not decision rule.

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