Skip to main content
Glama
Sign In

agent-tools (x402 + MCP + A2A directory)

by io.github.AgentTools-Cloud
OverviewDiscussionsAdmin

claim_service_url

Issue a fresh ownership token for one exact public HTTPS URL.

Authenticate in the MCP Authorization: Bearer header. Publishing and
verifying the token is required before editing; URL input alone grants no rights.

Args:
    url: Complete public HTTPS service URL, including its query when present.
    method: Optional proof method; otherwise inferred from the complete URL.

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": {
      "url": "<url>"
    },
    "name": "claim_service_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesComplete public HTTPS service URL, including its query when present.
methodNoOptional proof method; otherwise inferred from the complete URL.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations mark this as non-read-only and non-idempotent; the description corroborates by saying each call issues a *fresh* token. It also adds material facts annotations cannot convey — the Bearer header auth requirement and that mere URL submission confers no ownership — but says nothing about token lifetime or what happens to a previously issued token.

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 key scoping and auth facts are front-loaded in two short paragraphs. The Args section is pure duplication of the input schema and could be dropped without losing information.

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?

Given an output schema exists, return values need no explanation, and the description covers auth, prerequisites, and the write nature of the call. The remaining gap is the unstated lifecycle of the issued token, which matters for an explicitly non-idempotent operation.

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%, so the schema already documents both parameters. The Args block restates the schema descriptions verbatim rather than clarifying, for example, what values `method` accepts or how the method is inferred from the URL, so it adds no meaning beyond structured data.

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 names a specific verb and resource: "Issue a fresh ownership token" for "one exact public HTTPS URL." It also places the tool in a workflow (publish, then verify, then edit), which partially separates it from verify_service_url without naming that sibling outright.

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 states a clear prerequisite: the token must be published and verified before editing, and "URL input alone grants no rights." That establishes when the tool is needed, but it never explicitly contrasts this with verify_service_url or explains when a token should be refreshed instead of reused.

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

All agent-tools (x402 + MCP + A2A directory) toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources