Skip to main content
Glama

WritersLogic business agents

site-access-check

Site access: caller access rules against observed site facts — Checks whether an intended action on a website (read, crawl, submit, log in, ...) satisfies the access rules the caller supplies (robots rule read, terms clause, login present, rate-limit budget, captcha seen) against facts the caller observed, and says which rule blocked it or which fact is missing. For an agent deciding whether to proceed or ask. It is a reading of the caller's rules, not legal

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": {
      "action": "<action>",
      "rules": "<rules>",
      "evidence": "<evidence>"
    },
    "name": "site-access-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoReference instant (ISO date or instant) for evidence age; required only when a need sets maxAgeDays. The check never reads the clock.
rulesYesAccess rules: needs that must hold, or with forbid:true, conditions that must not apply.
actionYesThe intended action, matched against each rule's appliesTo.
evidenceYesObserved site facts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it makes clear the tool evaluates against facts the caller already observed rather than fetching anything, it discloses the output behavior (which rule blocked it, or which fact is missing), and it bounds scope ('a reading of the caller's rules, not legal [advice]'). It stops short of stating purity/determinism and the verdict vocabulary explicitly.

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?

Front-loaded with the purpose and then the mechanics, with no filler sentences. The opening 'Site access:' label is mildly redundant with the name, and the first sentence is dense with parenthetical examples, but overall it earns its length.

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?

For a 4-parameter rule-evaluation tool with no output schema, the description explains that a verdict and blocking rule/missing fact are returned, but not the shape of that result (status values, what 'witnesses' are, how optional rules are reported). An agent can decide to call it, but cannot anticipate the response structure from the description alone.

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 action, rules, evidence and asOf in depth, including mode/forbid/min/max/maxAgeDays semantics. The description adds the conceptual framing (rules are caller-supplied, evidence is what the caller observed, rules are matched by action) but no parameter-level detail beyond the schema; baseline 3 applies.

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 and resource: it checks an intended site action against caller-supplied access rules using caller-observed facts, and names the example action types (read, crawl, submit, log in) and rule kinds (robots rule, terms clause, login present, rate-limit budget, captcha). The closing line 'It is a reading of the caller's rules' implicitly separates it from a fetching/parsing tool like robots-check, but no sibling is named explicitly, so it stops short of a 5.

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?

'For an agent deciding whether to proceed or ask' gives a clear decision context, which is real usage guidance. However, it never states when NOT to use it, nor names an alternative for the adjacent job of actually fetching or parsing a site's robots/terms, which is a plausible sibling confusion given robots-check exists.

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.

Resources