Skip to main content
Glama

Tech Detect Coverage

tech_detect_coverage
Read-onlyIdempotent

Which technologies the website stack detector can recognise, listed by category, and what it cannot see. Use this before trusting a negative result, the detector covers a curated set, so a technology missing from an answer may simply be outside its coverage.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tech_detect_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly/openWorld/idempotent, so safety is covered. The description adds the genuinely useful behavioral fact that coverage is a curated set, which means absence in detector output is not proof of absence — the kind of false-negative caveat annotations cannot express.

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 sentences, front-loaded with what is listed and followed by the usage caveat; no filler. The second sentence runs two clauses together with a comma splice, a minor readability blemish rather than wasted content.

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, no-output-schema introspection tool, the description covers what is returned conceptually (recognised technologies by category, plus known gaps) and why it matters. An agent has enough to decide when to call it and how to interpret a negative detector result.

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 and there is no parameter meaning the description needs to carry. Nothing in the description misrepresents the call signature.

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 resource and scope: the set of technologies the website stack detector recognises, grouped by category, plus its blind spots. This implicitly positions it against the detector sibling ('tech_detect') without naming it, so an agent can infer the pairing but the description does not explicitly differentiate.

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 a concrete consumption rule — call it before trusting a negative result — which is real when-to-use guidance rather than vague context. It stops short of naming an alternative tool or stating exclusions, so it is clear but not exhaustive.

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.