Skip to main content
Glama
Sign In

Agentalog — Agent Auto Log

by com.agentalog
OverviewDiscussionsAdmin

API access

api_access
Read-onlyIdempotent

Monthly data package and private purchase status, without charging. MAT-only balance; pass prefix mat_. Catalog discovery and ordinary browsing are free. GPTBot, ClaudeBot, CCBot, Meta-ExternalAgent, Amazonbot, AhrefsBot and MJ12bot share a daily allowance of 1,000 reads per crawler family; over it the answer is 402 with the MAT reads package: US$ 1 for 1,000 reads for 30 days, with no automatic renewal. Buy it at POST /api/acesso and send its pass in X-API-Pass. The MAT allowance is separate from the company, address and procurement indexes.

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

Input Schema

NameRequiredDescriptionDefault
api_passNoMAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: daily crawler allowance, the 402 over-limit response, MAT pricing and no automatic renewal, and the X-API-Pass header requirement.

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 purpose is front-loaded in the first sentence, but the description then becomes dense with bot names, daily allowance details, pricing, and a purchase endpoint unrelated to invoking this specific tool. It is not bloated beyond usefulness, but some detail could be trimmed or moved to sibling documentation.

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

Completeness3/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 should clarify what the status check returns. It mentions monthly package and private purchase status, but does not describe the response fields, remaining balance, or expiry information, leaving the return behavior partly inferred.

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 description coverage is 100%, so the schema already documents the single optional api_pass parameter in detail. The description reinforces that the pass is MAT-only with the mat_ prefix, but it does not explain when the pass may be omitted or how the tool behaves without it, so this only modestly exceeds the baseline.

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 description identifies the subject as monthly data package and private purchase status, but it does not use a clear verb such as 'get' or 'check' and is phrased as a noun clause. The 'without charging' phrase hints at a read-only status check, but the distinction from api_access_buy is only implicit through the purchase endpoint mention.

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 implied by the status-oriented first sentence and by the note that catalog discovery and ordinary browsing are free. However, the description never explicitly says when to use this tool versus api_access_buy or api_usage, and it does not give concrete when-not conditions beyond the 402 over-limit behavior.

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 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