Skip to main content
Glama

COVER

COVER page section

cover_get_section
Read-onlyIdempotent

Returns one section of the COVER product page, such as key features, editions, use cases or industry standards. Use a title from cover_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": "cover_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

A3.8/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 by structured data. The description only adds that retrieval is scoped to a single section per call, which is modest incremental context rather than new behavioral disclosure.

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, no filler: the purpose and examples come first, the prerequisite second. 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 single-parameter, closed-world read tool with rich annotations, the definition covers what it does and how to supply the parameter. The only minor omission is what a returned section looks like (text, structured blocks, media), which matters somewhat since there is no output schema.

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 schema already gives "Key features" as an example, so the baseline is 3. The description does add extra valid-value examples and points to cover_list_sections as the authoritative source of titles, a real but incremental gain over 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 (Returns) and resource (one section of the COVER product page), and enumerates concrete section kinds (key features, editions, use cases, industry standards). It implicitly separates itself from cover_list_sections by being the content fetch rather than the listing, though it never explicitly contrasts with sibling page-area tools like cover_overview.

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 cover_list_sections" gives an explicit prerequisite and discovery step, which is exactly the guidance an agent needs before calling. It stops short of saying when to prefer a sibling (e.g. cover_overview) or what to do if the section is unknown, so no full alternative routing.

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