Skip to main content
Glama

list-wells

Read-onlyIdempotent

FREE catalog of Rainmaker wells (001–012, 014, 015, 016): id, name, tool, origin, price_usd, description, mcp_path. Also returns catalog_url. After picking a well, open {origin}/mcp directly.

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": "list-wells"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine value beyond that — the catalog is FREE, the ID set is fixed, and the {origin}/mcp follow-up step is disclosed — but says nothing about caching, freshness, or whether the listing is static.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool is and what it returns; the field enumeration is compact and skimmable. The parenthetical ID range is slightly noisy but carries real scoping information, so no sentence is wasted.

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 must carry the return-shape burden, and it does by naming all expected fields plus catalog_url. For a zero-parameter read-only catalog tool this is nearly complete; only freshness/pagination behavior for a fixed-list endpoint is unstated.

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?

Zero-parameter tool, so the baseline is 4. The description correctly implies no filtering input is needed by listing a fixed ID set and telling the agent to open {origin}/mcp for further interaction.

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 resource (Rainmaker wells), the exact ID range covered (001–012, 014, 015, 016), and enumerates the returned fields, so an agent knows precisely what it gets back. It does not explicitly contrast itself with the sibling 'catalog-url' or 'recommend-well', leaving differentiation to inference.

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?

The closing instruction 'After picking a well, open {origin}/mcp directly' gives a clear post-selection workflow, which implies usage context. However, there is no explicit statement of when to call this versus 'recommend-well' or 'catalog-url', so the routing decision is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources