Skip to main content
Glama
Sign In

Latchbell

by com.latchbell
OverviewDiscussionsAdmin

Read a business's website again

refresh_business_website
Read-only

For the business's own assistant answering a customer: when the customer asks about something on the business's website (a product, a price, a promotion) and what you have from it was read more than a day ago, read it again now. Returns each website's latest text and when it was read. At most every ten minutes per business; otherwise it returns what was read last.

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": {
      "business": "<business>"
    },
    "name": "refresh_business_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, the description discloses a rate limit (once per ten minutes per business), the fallback behavior when throttled (returns the last-read copy), the staleness threshold, and the shape of the return value (latest text plus read timestamp). That is meaningful operational context an agent could not get from 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.

Conciseness5/5

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

The scoping clause, the trigger, the rate limit, and the return value are all front-loaded in three tight sentences with no filler. Every sentence carries information the agent needs to decide and to interpret the result.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly explains what comes back and when throttling occurs, which covers the main gaps. It is slightly incomplete on the identifier format for 'business' and on why 'each website' is plural — whether a business may have multiple sites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'business' has 0% schema description coverage, so the description carries the full burden — yet it never says whether the value is a name, an ID, or a slug, nor what format is accepted. Only the incidental phrase 'per business' hints at its meaning, which is not enough for a required identifier.

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?

The description names a specific verb and resource — re-reading a business's website text — and scopes it to a concrete situation (stale cached content). It is clear what the tool does, but it offers no explicit differentiation from the similarly named sibling read_website_again, leaving the agent to infer the boundary.

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?

The trigger condition is unusually precise: use it when the customer asks about website content (product, price, promotion) and the existing copy is more than a day old. There is no explicit when-not-to-use statement or named alternative, so it stops short of a 5.

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

All Latchbell toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources