Skip to main content
Glama

Look up a recent scan

lookup_site
Read-only

Cheapest option: returns a scan made in the last 7 days if one exists, never scans. Needs a key.

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

Input Schema

NameRequiredDescriptionDefault
urlYesWebsite address, e.g. joesplumbing.com
api_keyNoOptional if your client sends Authorization: Bearer sw_agent_...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's added value is the 7-day staleness window, the 'if one exists' miss case, and 'Needs a key' auth requirement — all useful beyond the annotations. It still does not say what a miss actually returns (null, empty, or error), which is the key behavioral question for a cached lookup.

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?

One front-loaded sentence that leads with the cost/behavior differentiator and ends with the auth constraint; nothing is padding. It is slightly telegraphic ('Needs a key'), which reads more like a note than a structured description.

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 two-parameter read tool with a fully covered schema this is nearly adequate, but with no output schema the description should sketch what a returned 'scan' contains and what happens on a cache miss. Those two omissions are the remaining gaps.

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 url and api_key are already documented in the schema, and the baseline is 3. 'Needs a key' mildly reinforces the api_key parameter but adds no format or precedence detail beyond what the schema's Authorization: Bearer note already provides.

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 concrete verb and resource: returns a cached scan from the last 7 days, and explicitly says 'never scans', which separates it from scanning siblings. The phrasing 'Cheapest option' implies a cost tradeoff against other tools without naming them, so sibling differentiation is implied 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 Guidelines3/5

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

'Cheapest option' plus 'never scans' gives an implicit when-to-use rule (prefer this over a real scan to save cost). However, it never says what to do when no scan exists within 7 days — the obvious fallback of running check_website or full_audit is left to inference.

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