Skip to main content
Glama

check_agent_access

Pre-flight check: can an AI agent use this service at all, and on what terms? Answers from Fineprint's published leaderboard WITHOUT a scan and without spending quota — call this BEFORE scan_terms_of_service or before signing a principal up for anything. Returns the structured decision (automated access, account delegation, AI-agent terms, official-channels requirement) plus the overall friendliness verdict. If the service is unknown, run scan_terms_of_service on its terms 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": {
      "service": "<service>"
    },
    "name": "check_agent_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses that no scan is performed, no quota is consumed, and that the result is a structured decision plus a friendliness verdict. It doesn't cover auth requirements or freshness/staleness of the leaderboard data, which keeps it from a 5.

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

Conciseness5/5

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

Front-loaded with the core question, then the cost/side-effect guarantee, then the return shape, then the fallback. Every sentence adds information; no redundancy with the title or schema.

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?

For a one-parameter read-only lookup with an output schema, the description covers purpose, side-effect guarantees, return shape, and the fallback path. Return values need not be detailed further since an output schema exists.

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 0% for the single 'service' parameter, so the description must compensate. It implies a service identifier (and that a terms URL exists for unknown services) but never says whether 'service' should be a name, domain, or URL, leaving format ambiguity.

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?

States a specific question ('can an AI agent use this service at all, and on what terms?') and names the data source (Fineprint's published leaderboard). It distinguishes itself from the closest sibling by saying it works 'WITHOUT a scan' and 'without spending quota', unlike scan_terms_of_service.

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

Usage Guidelines5/5

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

Explicit sequencing: 'call this BEFORE scan_terms_of_service or before signing a principal up for anything', plus a concrete fallback ('If the service is unknown, run scan_terms_of_service on its terms URL'). Both the when-to-use and the when-to-instead-use are named.

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.