Skip to main content
Glama

north_limits

Check the owner-defined spending limits that determine what the local wallet can pay automatically, so agents can verify payment permissions before transacting.

Instructions

What the owner lets this wallet pay by itself.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether the tool reads or mutates limits, what permissions are needed, or what happens on invocation. The phrase hints at a policy concept but gives no operational behavior.

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?

It is extremely short with no wasted words, but the single sentence fragment is not front-loaded with an action and is under-specified rather than crisp. It earns little beyond identifying the topic.

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

Completeness2/5

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

With zero parameters, no annotations, and no output schema, the definition should at least clarify that it returns the wallet's current autonomous payment limits. It leaves the agent guessing about the response shape and whether the limits are asset-specific.

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, so the baseline is 4 under the rubric. The description neither needs nor adds parameter detail.

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

Purpose3/5

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

The fragment identifies the concept—owner-authorized autonomous payment limits—but never states a verb or explicitly says it retrieves limits. It is more informative than a tautology, yet an agent cannot confidently tell whether this reads, sets, or explains limits.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of sibling tools such as north_balance or north_pay. The agent must infer that this is a lookup of spending allowances rather than a payment action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.