Skip to main content
Glama

Odile Machine Access

Search Machine Access contracts

gate_search_access
Read-onlyIdempotent

Search APIs listed in Odile Machine Access. Each is a domain-verified access contract: the calls an AI agent may make, the owner's price for each in credits (1 credit = USD 0.10; 0 is free), rate and daily limits, and a connect URL. Read-only; connecting is an HTTP POST to the connect URL.

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

Input Schema

NameRequiredDescriptionDefault
maxNoAt most this many results (default 10)
queryNoWords to look for in the name, description, host or allowed calls, e.g. "email check"; leave out to list every contract

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 the description reinforces read-only while adding genuinely new behavior: the credit-to-USD conversion (1 credit = USD 0.10), that 0 means free, and that connecting is a POST to the returned URL. It does not cover ordering, truncation beyond the max cap, or result totals.

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 compact sentences, front-loaded with the action and immediately followed by the payoff (what a contract contains) and a usage caveat. Every sentence carries information an agent needs.

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, fully documented search with no output schema, the description is nearly complete: it explains result contents, pricing semantics, and how to act on a result. Minor gaps remain around result ordering and what happens when the catalog exceeds the max result cap.

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 coverage is 100%, so both parameters are already documented, including the guidance that omitting query lists all contracts. The description adds no syntax, matching behavior, or formatting detail beyond the schema; baseline 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 ("Search APIs listed in Odile Machine Access") and then defines what a result actually is: a domain-verified access contract carrying allowed calls, per-call credit price, rate/daily limits, and a connect URL. An agent knows exactly what this tool returns without opening the schema.

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?

The scope boundary is clear: this tool searches contracts and is read-only, while actually using a contract is a separate HTTP POST to the connect URL. It also notes the query can be omitted to list every contract. No explicit exclusions or named alternatives, but there are no siblings, so little is left to inference.

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