Skip to main content
Glama

mcpsense_discover

Read-only

Discovers common MCP configuration paths within an approved project and returns only their locations, without exposing file contents or starting servers.

Instructions

Find common existing MCP configuration paths inside the approved project. Returns paths only; does not reveal file contents or start configured servers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcpsense_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description earns credit beyond that by naming two concrete negative behaviors: it does not reveal file contents and does not start configured servers. That directly answers the agent's likely follow-up questions about side effects and data exposure.

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 sentences with no filler. The positive capability and its scope come first, and the two negative constraints follow immediately, which is the right ordering for a read-oriented discovery tool.

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 zero-parameter tool with no output schema, the definition covers purpose, scope, and side-effect boundaries. The only remaining gap is the shape of the return value: 'returns paths only' says what kind of data comes back but not whether it is a list, a map, or how empty results are represented.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing parameter-level the description could add. The description correctly avoids inventing arguments that do not exist.

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 and resource: 'Find common existing MCP configuration paths' scoped to 'the approved project'. That is far more precise than a bare 'discover', and the phrase 'paths only' hints at how it differs from content-oriented siblings, but it never names or contrasts with mcpsense_scan or mcpsense_verify, leaving the agent to infer the split.

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 phrase 'inside the approved project' and by the fact that it locates rather than inspects. There is no explicit statement of when to reach for this versus mcpsense_scan or mcpsense_checks, and no prerequisites or exclusions are given, so the agent must infer the routing.

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