Skip to main content
Glama
Agency MCP Server

Agency MCP Server

Answerability score

score_answerability
Read-only

Scores a page from 0–100 for answerability by checking question headings, early answers, FAQ markup and paragraph length, then suggests answer-first rewrites.

Instructions

Deterministic 0-100 score of how easily answers can be lifted from a page: question-form headings, answer within the first 50 words, FAQ markup and paragraph length, with answer-first rewrite suggestions.

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": {
      "client": "<client>",
      "url": "<url>"
    },
    "name": "score_answerability"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute URL inside the client's allowlist.
clientYesClient id from the server's config (dental, cafe, plumber).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered; the description adds real behavioral value beyond that by promising a deterministic (reproducible) 0-100 scale and stating that answer-first rewrite suggestions accompany the score. It does not disclose fetch/rate-limit behavior or whether the analyzed page is retrieved live, which keeps it short of a 5.

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?

A single front-loaded sentence that leads with the deliverable (a 0-100 score) and then the criteria, with no filler. The embedded factor list makes it dense but every clause carries information; a slightly cleaner separation of score versus suggestions would earn a 5.

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?

With only two fully described parameters and no output schema, the description carries the burden of explaining the return value, which it does (numeric score plus rewrite suggestions). Nothing an agent needs in order to invoke it correctly is missing, though it omits whether the score is per-URL only or comparable across runs.

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%, with url (absolute URL inside the client's allowlist) and client (config id) both documented, so the baseline is 3. The description confirms the unit of analysis is a single page but adds no clarification on the allowlist constraint or the client scoping beyond what the schema already says.

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 ('Deterministic 0-100 score of how easily answers can be lifted from a page') and enumerates the exact signals scored (question-form headings, answer in first 50 words, FAQ markup, paragraph length). It never names or contrasts a sibling such as audit_page, which audits a page for other criteria, so sibling differentiation is left implicit.

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?

Usage is only implied: an agent can infer this is the tool for judging answer-extractability of a single page, but there is no explicit when-to-use statement, no prerequisites, and no guidance on choosing it over audit_page or answer_engine_visibility. The AEO-flavored framing helps, but routing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.