Skip to main content
Glama

SURESOFT CT

CT FAQ

ct_search_faq
Read-onlyIdempotent

Searches the frequently asked questions on the CT product page. Leave query empty to list every question.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords to look for, e.g. "MISRA" or "air-gapped".

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, non-destructive, and closed-world, so the safety profile is fully covered and the description needn't repeat it. The description does add one genuinely behavioral fact beyond annotations: an empty query returns the full question list. It says nothing about result shape (question only vs. question plus answer) or result volume, leaving a modest gap.

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, with the core action front-loaded and the optionality rule second. No filler, no restated annotation boilerplate; every sentence carries information the agent needs.

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 search tool with rich annotations and no output schema, the definition covers what it does, how to enumerate, and what to query against. The only untold detail is whether matches return answers or just questions, which is minor for a tool of this simplicity.

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 query parameter is already documented with examples ("MISRA", "air-gapped"), so the baseline would be 3. The description earns the extra point by explaining the semantic consequence of the optional parameter: omitting it changes the call from a search into a full 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?

"Searches the frequently asked questions on the CT product page" gives a specific verb (searches) and a specific resource (the FAQ on the CT product page), which is distinguishable from content-oriented siblings like ct_overview, ct_get_section, and ct_resources. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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?

The description gives one concrete usage rule - leave query empty to list every question - which tells the agent how to enumerate rather than search. It does not say when to prefer this tool over ct_get_section or ct_overview for product information, so routing guidance is only implied.

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