Skip to main content
Glama

SigLint — HTTP Message Signature Doctor

signcheck_pricing

返回当前价格、收款方、付款凭据形状与调用示例。不收费。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure alone. It usefully declares that the call is free ("不收费") and enumerates returned content, which signals a non-mutating informational read. It does not state idempotency, whether price can change between calls, or the response format, leaving real gaps for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the payload contents are front-loaded before the cost note. Every clause carries information an agent would otherwise have to guess.

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 info tool, the description covers the essentials an agent needs: what comes back (price, payee, credential shape, example) and that calling it is free. Only the exact response structure and any price-stability caveat are left unspecified, which is a minor gap at this complexity.

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, and the schema is empty with additionalProperties=false and 100% coverage, so there is nothing for the description to disambiguate. Per the baseline for a 0-param tool, a 4 is appropriate.

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?

The description uses a specific verb ("返回" / returns) and names concrete resources: current price, payee, payment credential shape, and a call example. An agent can tell this is a read-only info lookup about pricing. It does not, however, distinguish itself from the sibling signcheck_verify, so it falls short of a 5.

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: 'returns current price ... and a call example' suggests calling this before performing a paid verification, and '不收费' (free of charge) hints there is no cost to calling it. There is no explicit when-to-use statement, no exclusions, and no routing to or from signcheck_verify.

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