Skip to main content
Glama

SURESOFT CT

CT page section

ct_get_section
Read-onlyIdempotent

Returns one section of the CT product page, such as key features, editions, use cases or industry standards. Use a title from ct_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": "ct_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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds that only a single section is returned and where valid titles come from, but says nothing about behavior on an unknown title or the shape of the returned content.

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?

Two short sentences, with the return scope front-loaded before the usage hint. Every clause carries information; only a minor gap is the absence of any note about what the returned section looks like.

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-only lookup with rich annotations and no output schema, the description covers what it returns and how to source the input. A brief note on the response format or behavior for invalid titles would make it complete.

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 schema already documents the single parameter with an example. The description still adds meaning by enumerating plausible section values and specifying that titles should originate from ct_list_sections, which is more than the schema says about accepted values.

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 one section of the CT product page," and grounds it with concrete section examples (key features, editions, use cases, industry standards). It implicitly distinguishes itself from ct_list_sections by dealing with a single section rather than a listing, though it never names ct_overview as the whole-page alternative.

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?

Gives an explicit prerequisite workflow: "Use a title from ct_list_sections," which tells the agent how to obtain a valid input before calling. It stops short of stating exclusions, such as when to prefer ct_overview for the full page instead of a single section.

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