Skip to main content
Glama
Sign In

Excession Labs: site search and security test requests

by ai.excessionlabs
OverviewDiscussionsAdmin

Search excessionlabs.ai

search_site
Read-onlyIdempotent

Search the public pages and research notes on excessionlabs.ai. Returns titles, URLs and one-line summaries.

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": {
      "query": "<query>"
    },
    "name": "search_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1 to 20, default 8)
queryYesWords to search for, for example 'security assessment' or 'authorization testing'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Words to search for, for example 'abliterated model' or 'Claude Code setup'"New value: +"Words to search for, for example 'security assessment' or 'authorization testing'"
  2. First observed

TDQS

A3.8/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 that by disclosing the content scope (public pages plus research notes) and the return shape (titles, URLs, one-line summaries) despite no output schema existing.

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, zero filler, with the search scope front-loaded before the return-value note. Every sentence 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 two-parameter read-only search with full schema coverage and complete annotations, the description covers what is searched and what comes back. Minor gaps (result ordering, whether excerpts are matched snippets) are not material to calling it correctly.

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%, with both query and limit fully documented including bounds and an example. The description adds no parameter meaning beyond the schema, so the 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 ("Search") plus a precisely scoped resource ("public pages and research notes on excessionlabs.ai"), which distinguishes it implicitly from get_page. It stops short of naming any sibling or the condition that separates searching from direct page retrieval.

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?

Usage is implied by the scope statement — search the site's public content — but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to get_page for known-URL retrieval. The agent must infer the boundary.

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