Skip to main content
Glama

Is an agent's newest payment in character (free, advisory)

agent_pattern
Read-onlyIdempotent

Use this to ask whether an agent's newest payment is in character; on its own it is not a pre-payment check (pay_check is). The out-of-character score of an agent's newest counted payment against its own earlier payments (behaviour.out_of_character.v3 since 7 Nov 2026: amount out of its distribution, a new payee at a new size, a never-paid plain key, a probe then a large payment, a look-alike address, an approval change, off its rhythm), with the reasons that fired, how many of its last 30 days of payments scored notable or major, and the market's rates. Levels are none / notable / major; a level is a pattern for a human to read, never a verdict, and nothing is blocked by us from it (advisory since 1 Nov 2026). Every figure carries its measurement time and definition id.

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": {
      "agent": "<agent>"
    },
    "name": "agent_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent token id, act_8453_N, slug or bound wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behaviour beyond that: the level vocabulary (none/notable/major), the explicit 'pattern not verdict, nothing blocked' semantics, the model version and effective date, and the fact that every figure carries a measurement time and definition id. That is precisely the context annotations cannot express.

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

Conciseness3/5

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

The use case is front-loaded, but the body is one very long sentence built from stacked parentheticals, which makes the list of fired reasons hard to parse on first read. All the content is substantive; the packaging costs readability.

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 still tells the agent what comes back: which reasons fired, how many of the last 30 days of payments scored notable or major, and market rates, plus the level scale. Nothing an agent needs to interpret the response correctly is left unstated.

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?

There is a single parameter at 100% schema coverage, which already enumerates the accepted forms (token id, act_8453_N, slug or bound wallet). The description adds no syntax or format guidance beyond that, so the baseline of 3 applies.

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 first clause names a specific question about a specific resource: whether an agent's newest payment is in character, scored against its own earlier payments. It also names the sibling it is not (pay_check) at the point of definition, so an agent can separate the two without opening either schema.

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 gives an explicit when-not ('not a pre-payment check (pay_check is)') and makes clear this is advisory only, with nothing blocked. It does not position the tool against the other behavioural siblings (agent_record, agent_statement, agent_stability), so the routing guidance is clear but not exhaustive.

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.