Skip to main content
Glama

MedaRep

The rep's accounts

my_accounts
Read-onlyIdempotent

Every account the rep (and their team) has logged: where it stands per product segment, the share of a customer's cases held and the room to grow, when it was last touched, and the next follow-up. Filter by status or by days untouched; sort=room puts the customers with the most cases not yet won first. Use it for a pipeline review, a list of neglected accounts, or where to expand.

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

Input Schema

NameRequiredDescriptionDefault
sortNodue (default): overdue follow-ups first, then longest untouched. room: most room to grow first.
limitNoDefault 25.
statusNo
untouched_daysNoOnly accounts with nothing logged in 30, 60 or 90 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the data scope is the rep plus their team, records carry computed fields like share-of-cases and room to grow, and sort order determines what surfaces first. Auth requirements and result size are not discussed, but they matter less for a read-only list.

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?

Front-loaded with what comes back, then filtering/sorting mechanics, then use cases — a sensible information order with no filler sentences. The record-field list is long but each item is a distinct, decision-relevant attribute rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the returned fields, so an agent knows what it will get before calling. All four parameters are optional and the defaults (due, limit 25) are documented in the schema, leaving nothing material unstated for a read-only listing tool.

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?

Schema coverage is 75%, so the schema does most of the work, but the description adds real meaning beyond it: sort=room is explained as 'customers with the most cases not yet won first', which clarifies the otherwise opaque enum value, and it groups the two filters by intent. untouched_days' allowed values (30/60/90) live only in the schema, so the description does not fully compensate.

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 the resource (every account the rep and their team have logged) and enumerates what each record carries — segment standing, share of cases held, room to grow, last touch, next follow-up. That is far more specific than a restated title. It stops short of 5 because it never names a sibling (e.g. my_customers) to sharpen the boundary between 'accounts' and 'customers'.

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 three concrete use cases (pipeline review, neglected accounts, expansion targets) and ties the filters to them — status/untouched_days for neglected accounts, sort=room for expansion. There is no explicit when-not or named alternative tool, which keeps it out of 5 territory.

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