Skip to main content
Glama

Attify

Ask Attify

ask_attify
Read-onlyIdempotent

A plain-language question about the public sample audit or a published vendor's score, answered from that data only: numbers copied with their intervals and tier, every claim cited (verdict fields, finding ids, evidence ids), "not in the data" instead of a guess. Requests for advice on raising a score, and for private data (brand names, source ids), are refused.

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": {
      "question": "<question>"
    },
    "name": "ask_attify"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorNoA published vendor's profile slug, e.g. "acme-ai-resolve-bot". Omit for the public sample audit (synthetic demo data, labelled as such).
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, closed-world, non-destructive); the description adds a real answer contract: numbers copied with their intervals and tier, every claim cited via verdict fields, finding ids and evidence ids, and "not in the data" rather than a guess. It also discloses two refusal classes, which is behavior an agent could not infer from annotations.

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 densely packed sentence with a colon-delimited enumeration of the grounding rules, front-loaded on purpose before the refusal clause. Every clause carries information, though the nested parenthetical makes it harder to scan than a two-sentence split would be.

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 two-parameter tool with no output schema, it covers purpose, grounding rules, citation behavior, the no-data fallback and refusal cases. The main residual gap is what the answer actually looks like in structure, since there is no output schema to fall back on.

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 50%: the vendor slug is documented in the schema, but the question parameter has only a maxLength. The description compensates by defining the question domain (plain-language, about the public sample audit or a published vendor's score) and by flagging which questions are refused, though it adds no guidance on phrasing length or granularity.

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 concrete verb and resource: a plain-language question about the public sample audit or a published vendor's score, answered from that data only. That scope implicitly separates it from structured siblings like get_verdict or list_findings, but no sibling is named explicitly, so it stops short of full differentiation.

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 clear context for use (plain-language questions over audit results and published scores) and explicit exclusions: requests for score-raising advice and for private data such as brand names or source ids are refused. It does not point the agent at an alternative for those refused cases or for structured lookups.

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