Skip to main content
Glama

signafAIde

Get the signafAIde service's public keys

signafaide_service_keys
Read-only

Use this when the user wants the signafAIde service's public signing keys, for example to check a verification pack independently or to see which key co-signed a record. Returns every service key with its key id, its public key and the dates it was valid, the address where the same list is published (https://signafaide.co.uk/.well-known/signafaide-keys.json), and the command that verifies a pack with it. Public information only: it takes no input and changes nothing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description's 'takes no input and changes nothing' is largely redundant with those. What it does add beyond structured data is the response shape: every key with key id, public key, valid dates, the canonical published URL, and the verification command, which is useful since there is no output schema.

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 purpose and triggers are front-loaded in the first clause, and the remaining text is spent on return contents rather than filler. It is slightly dense and the return-format list could be tightened, but every element carries information an agent can act on.

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?

For a no-parameter, read-only tool with no output schema, the description supplies exactly the missing pieces: what the response contains, where the same data is published, and how it is used for verification. Nothing needed to invoke or interpret it correctly is absent.

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?

There are zero parameters, so the baseline is 4, and the description correctly confirms 'it takes no input'. No further parameter meaning is needed for an input-free tool.

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?

The description names a specific verb and resource ('get the signafAIde service's public signing keys') and frames the intent with two concrete scenarios: independently checking a verification pack, or identifying which key co-signed a record. That makes it distinguishable from the sibling verify_pack, which performs the verification rather than returning raw keys.

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?

It opens with an explicit triggering condition ('Use this when the user wants...') and gives two motivating examples, which is strong when-to-use guidance. It stops short of naming when-not to use it or explicitly pointing to signafaide_verify_pack as the alternative, so the contrast is implied rather than stated.

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