Skip to main content
Glama

View customer dashboard in Pike13

pike13_view_customer_dashboard
Read-onlyIdempotent

View customer dashboard 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_view_customer_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, and the description adds meaningful behavior beyond them: it 'opens nothing by itself' and returns descriptive guidance rather than performing navigation. That is an important non-obvious trait for an agent that might otherwise expect an action to occur. The trailing sentence about Pike13's official APIs is vague and adds no actionable behavior.

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 guidance is front-loaded and clear, but the opening clause enumerating 'ChatGPT, Claude or any AI agent' is filler, and the closing sentence about Pike13's Core, Reporting and Webhooks APIs is tangential and could mislead an agent into expecting API-level behavior. Trimming those two fragments would sharpen the definition without losing information.

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 zero parameters, no output schema, and full annotation coverage, the description needs mainly to explain what comes back and what to do next, and it does both (step-by-step instructions, then cotlet_browser_* execution). The remaining gap is guidance on when to prefer the record-search or list-filtering Pike13 siblings over this dashboard walkthrough.

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 under the rubric. The description introduces no parameter concepts and nothing is missing on that front.

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 names a specific verb and resource (view customer dashboard in Pike13) and immediately clarifies the tool's real output: step-by-step instructions of screens, buttons, and fields, not the action itself. It does not compare against the other Pike13 siblings (pike13_search_customer_records, pike13_filter_and_sort_customer_list), so an agent must infer which Pike13 tool to pick for which goal.

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?

It gives an explicit sequencing rule: this tool returns the how-to, then the agent should perform it with cotlet_browser_* tools in the Pike13 Cloud Browser. That is a clear use context and a named class of alternatives. It stops short of stating when NOT to use it (e.g., for searching or filtering customer records), leaving the boundary with the other pike13_* siblings unstated.

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