Skip to main content
Glama
Sign In

Excession Labs: site search and security test requests

by ai.excessionlabs
OverviewDiscussionsAdmin

Get a page as Markdown

get_page
Read-onlyIdempotent

Read one public page of excessionlabs.ai as Markdown. Use a path from search_site or llms.txt.

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": {
      "path": "<path>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPage path or full URL on excessionlabs.ai, for example '/', '/about/' or '/security-assessment/'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / path / description
      Previous value: -"Page path or full URL on excessionlabs.ai, for example '/', '/about/', '/pricing' or '/blog/deepseek-api-guide/'"New value: +"Page path or full URL on excessionlabs.ai, for example '/', '/about/' or '/security-assessment/'"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them by scoping access to public pages only and announcing that the payload is Markdown, which shapes how the agent should consume the result.

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?

Two short sentences, no filler, with the core action front-loaded and the input-sourcing hint second. Every clause earns its place.

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?

For a single-parameter read tool with rich annotations, the definition covers action, scope, input source and output format. Minor gaps remain around failure behavior for non-public or unknown paths, and there is no output schema to lean on, but nothing essential to invocation is missing.

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

Parameters4/5

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

Schema coverage is 100% and the path parameter already documents examples and full-URL support, so the baseline is 3. The description adds provenance (derive the value from search_site or llms.txt), which tells the agent where a valid value comes from rather than just its shape.

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 verb (Read), a specific resource (one public page of excessionlabs.ai) and the return format (Markdown). Naming search_site as the path source also implicitly distinguishes it from the search sibling, so an agent can pick correctly without opening either schema.

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?

"Use a path from search_site or llms.txt" gives clear guidance on the prerequisite workflow before calling. It stops short of explicit exclusions (e.g. what to do when a page is not public or the path is invalid), but the intended context is unambiguous.

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

All Excession Labs: site search and security test requests 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