Agentalog — Agent Auto Log

Check tool

check_tool

Read-onlyIdempotent

Before installing a remote MCP server, check its address: signals from the address itself (consumer tunnel, no TLS), the catalog listings with that address or host and their security level, and facts about its domain. Never visits the address. Send the endpoint URL. The answer never contacts that address: it reads what our weekly visits measured and what our domain data knows. address_signals comes from the address alone (consumer tunnel, http:// without TLS). records lists the catalog listings with this exact address first (exato: true), then up to 20 others on the same host, each with its level and signals; same_host counts them all. domain has the facts about the host's domain. An address outside the catalog answers no_catalogo: false and register: submit it to get it reviewed. Cached for 5 minutes.

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

Input Schema

Name	Required	Description
`url`	Yes	The http(s) endpoint of the MCP server, without credentials.
`api_pass`	No	MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.
`retry_key`	No	Optional retry key, up to 80 ASCII characters; same read for five minutes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / api_pass

Added value: +{
+  "description": "MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.",
+  "type": "string"
+}

Changed1 schema field changedOct 15, 2026

removedInput schema / properties / api_pass

Removed value: -{
-  "description": "MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.",
-  "type": "string"
-}

AddedOct 7, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already mark it read-only, idempotent, and non-destructive, and the description adds concrete behavior: it never contacts the address, uses weekly visit measurements and domain data, returns fields such as address_signals, records, and domain, handles uncatalogued addresses via no_catalogo and register, and caches for 5 minutes. There is no contradiction with the annotations.

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 opening is front-loaded with purpose and a return overview, but the no-contact guarantee is repeated in 'Never visits the address' and 'The answer never contacts that address,' and 'Send the endpoint URL' is redundant. The output-field detail is useful, but the description is not optimally concise.

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?

There is no output schema, so the description carries the return-value burden; it explains address_signals, records and same_host, domain, no_catalogo and register, and caching. Combined with 100% schema coverage for the three inputs, an agent has enough information to call and interpret the tool.

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 url, api_pass, and retry_key. The description reinforces that the url is the endpoint to send and mentions the 5-minute cache, but it adds no meaningful semantics for api_pass or retry_key; baseline 3 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?

States a specific verb (check) and resource (a remote MCP server's address), and enumerates the outputs: address signals, catalog listings, and domain facts. It does not name a sibling tool such as listing_security or mcp_index_signals, so the distinction from siblings is implicit rather than explicit.

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?

Gives a clear trigger: use it before installing a remote MCP server. It does not say when not to use it or name an alternative tool for adjacent checks, so it falls short of explicit alternatives and exclusions.

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

All Agentalog — Agent Auto Log tools Inspect

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.