Skip to main content
Glama

Search customer records in Pike13

pike13_search_customer_records
Read-onlyIdempotent

Search customer records in the user's own Pike13 account from ChatGPT, Claude or any AI agent. Returns how to do it in Pike13 step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Pike13 Cloud Browser. Pike13's official API: Pike13 documents Core, Reporting and Webhooks APIs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint and idempotentHint are consistent with "opens nothing by itself," and the description adds real context beyond the annotations: the return value is procedural guidance with concrete UI elements, and a browser session is required to actually perform the action. Minor gap in not saying how long or detailed the guidance is, but the safety and side-effect profile is unambiguous.

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

Conciseness3/5

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

The core sentence is front-loaded and useful, but "from ChatGPT, Claude or any AI agent" is filler that adds no selection value, and the trailing "Pike13's official API: Pike13 documents Core, Reporting and Webhooks APIs" is a dangling fragment with no clear relevance to invoking this 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?

With no parameters and no output schema, the description carries the burden of explaining the return shape, and it does: step-by-step screens, buttons, and fields. It also correctly scopes the tool as guidance-only and points to the browser tools for execution, leaving only minor ambiguity about how the guidance is targeted.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description does not explain how the tool knows which task to guide on given no input, which is a legitimate open question for a zero-arg tool.

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?

The description makes the real behavior explicit: it returns step-by-step instructions (screens, buttons, fields) for searching customer records rather than executing a search, and it names the cotlet_browser_* tools as the execution path. The opening phrase "Search customer records" reads like a live query, so the clarification has to do corrective work, but the net purpose is still clear.

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?

It states the follow-up path ("then do it with the cotlet_browser_* tools in the user's Pike13 Cloud Browser"), which is genuine when/how guidance. It does not distinguish this from the more specific Pike13 siblings in the catalog, such as pike13_view_customer_dashboard or pike13_filter_and_sort_customer_list, so the agent must infer which entry point fits.

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