Skip to main content
Glama
Sign In
api-mcp

api-mcp

by Hassan-Jamal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Scan codebase for API endpoints

scan_endpoints

Scans a project directory for API endpoints from client calls and server routes, then generates a discovery report and endpoints.json.

Instructions

Recursively scans a project directory (React Native, web, Flutter, or backend) for API endpoints — fetch/axios/Dart-http/Dio client calls and Express/NestJS/Flask/FastAPI/Spring server routes. Writes a discovery report and endpoints.json.

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": "scan_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute or relative path to the project root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.11

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It describes the recursive scanning and file writing actions but does not mention if it is read-only, requires permissions, or has side effects beyond writing files. This is minimal transparency.

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 description is extremely concise with two sentences, front-loading the main action and then the output. Every sentence adds value without redundancy.

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

Completeness3/5

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

Given the absence of output schema and annotations, the description could provide more detail on the content of the report or endpoints.json, and how the tool interacts with sibling tools. It is adequate but not comprehensive.

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 the schema already documents the 'path' parameter. The description adds no additional meaning, examples, or constraints beyond the schema, resulting in a baseline score of 3.

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 tool recursively scans project directories for API endpoints, listing specific client and server technologies, and outputs a report and JSON file. This distinguishes it from sibling tools like detect_base_url or detect_openapi.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide explicit guidance on when to use this tool versus alternatives such as detect_base_url or full_audit. It lacks when-to-use, when-not-to-use, or prerequisite information.

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

Deploy Server

Other Tools