Skip to main content
Glama
Sign In

Scrappa

by co.scrappa
OverviewDiscussionsAdmin

Find API endpoints

search-endpoints
Read-onlyIdempotent

Find Scrappa API endpoints by keyword. Returns matching endpoint names, descriptions, and parameters. Use a returned endpoint name with Call an API endpoint.

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-endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of endpoints to return (default 25, max 50)
queryYesSearch term to find endpoints (e.g. "google maps reviews", "flights", "linkedin profile")
offsetNoNumber of matching endpoints to skip, to read the next page (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum number of endpoints to return (default 25, max 50)",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of matching endpoints to skip, to read the next page (default 0)",
+  "type": "integer"
+}
  4. First observed

TDQS

A4/5.0
Behavior3/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 the return shape (names, descriptions, parameters), which is useful, but says nothing about pagination behavior despite limit/offset existing, nor about result ordering or empty-result handling.

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?

Three short sentences, front-loaded with purpose, followed by return contents and the downstream usage hint. No filler and every sentence carries information.

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 usefully summarizes the return fields, and the workflow linkage to call-endpoint closes the main gap. Pagination mechanics are left entirely to the schema, which is a minor but real omission for a 3-param search tool.

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 query, limit, and offset are all fully documented in the schema including defaults and examples. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 and resource ('Find Scrappa API endpoints by keyword') and explicitly names what it returns. It also distinguishes itself from the sibling call-endpoint by telling the agent to use a returned name with that tool.

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?

Gives clear context: search first, then feed the returned endpoint name into 'Call an API endpoint'. The workflow relationship to the sibling is made explicit, though no when-not-to-use or exclusion criteria are given.

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

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