Skip to main content
Glama

signafAIde

Check a signafAIde auditor link

signafaide_check_auditor_link
Read-only

Use this when the user has a signafAIde auditor link that an organisation shared with them and wants to know what it covers and whether the records in it check out. Give the whole link (it starts with https://signafaide.co.uk/app/audit/) or only its token. Returns the organisation and project names, the environment, the agents and the period the link covers, when the link expires, how many records and agents are in scope, the public timestamp status, each of the 12 verification checks with its result (pass, pending, not checked or fail), tool coverage notes, and the command for checking the records independently. Only links of this service are accepted: a link to any other address is refused, and no request is made to that address. An unknown, revoked or expired link returns a message that says so. It never returns the inputs or outputs of the agent's tool calls, and it changes nothing. The result is evidence about the records, not a certification.

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": {
      "link": "<link>"
    },
    "name": "signafaide_check_auditor_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe auditor link, https://signafaide.co.uk/app/audit/<token>, or only the token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), yet the description adds substantial context: no request is made to non-matching addresses, unknown/revoked/expired links return an explanatory message, tool-call inputs and outputs are never exposed, and nothing is changed. It also frames the result as evidence rather than certification, setting expectations the annotations cannot convey.

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?

The trigger condition and accepted input are front-loaded, followed by the return contents and the failure/limitation notes. It is a long paragraph, but nearly every sentence carries information; the only mild excess is the enumeration of returned fields, which is arguably necessary given there is no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden of describing the return value, and it does so thoroughly: organisation, project, environment, agents, period, expiry, scope counts, timestamp status, all 12 verification checks with their states, coverage notes, and the independent verification command. It also covers failure modes and privacy boundaries, leaving little an agent needs to guess.

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 coverage is 100% and the single parameter's schema description already states that the full link or only the token is accepted. The description repeats this rather than adding syntax, encoding, or validation detail beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('check a signafAIde auditor link ... what it covers and whether the records in it check out') and pins down the domain (https://signafaide.co.uk/app/audit/). This is clearly distinguishable from siblings like signafaide_verify_pack or signafaide_explain_error, which concern different artefacts.

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 trigger condition: the user has an auditor link an organisation shared with them and wants to know what it covers and whether the records check out. It also states an input constraint (only this service's links; other addresses are refused). It does not explicitly name a sibling or say when another tool would be preferable, so it falls short of a 5.

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