Skip to main content
Glama
Sign In

IndexMachine

by co.indexmachine
OverviewDiscussionsAdmin

Read one site

site_summary
Read-only

One site in full: page counts, today's Request indexing quota (about 10 a day, reset at midnight Pacific), the median days from a first request to indexing, and up to 30 days of counts.

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": {
      "site": "<site>"
    },
    "name": "site_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: its id (a UUID) or its domain, such as example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description provides highly valuable behavioral context beyond annotations, including the indexing quota (approx. 10 a day), its reset schedule (midnight Pacific), and the data retention limit of up to 30 days for counts.

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 tool is defined in a single, highly packed sentence that efficiently communicates the breadth of information provided and its scope.

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?

Given the single input parameter and high schema coverage, the description is fully complete. It explains not only what data is provided but also the operational constraints, like the quota and time-window limits.

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?

With 100% schema description coverage, the schema adequately defines the single 'site' parameter. The description merely confirms the input flexibility (UUID or domain), falling back to the baseline score.

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?

The description clearly states the function as providing a comprehensive summary ('One site in full') and lists the exact data points returned, such as page counts, quota, and median indexing days.

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?

Although it does not explicitly name siblings, the description defines its scope as a comprehensive summary, which helps the agent distinguish it from granular checks like `list_pages` or individual request checks.

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

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