Skip to main content
Glama

MedaRep

Who to call today

my_day
Read-onlyIdempotent

The rep's day, as the site's Today page has it: follow-ups due, then the surgeons with a reason to call across their saved territories, their own accounts and what is new this week first, each with why and the step to take. Start a morning or a route plan here. Counts toward the plan's daily territories like opening Today.

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_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsNoHow many calls to plan; default 5.

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?

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing the ordering logic of the result set and, importantly, that invoking it has a side effect on the plan's daily territories ('Counts toward the plan's daily territories like opening Today') — a non-obvious trait for a read-only tool. It stops short of explaining freshness or caching of the underlying Today page.

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 purpose is front-loaded, but the middle clause ('the surgeons with a reason to call across their saved territories, their own accounts and what is new this week first') is a dense stack of qualifiers that is hard to parse on one read, and the closing 'like opening Today' is a comparison rather than information. It is compact but not clean.

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 one-parameter, read-only tool with no output schema, the description does the necessary work of describing the shape, ordering and per-item framing ('each with why and the step to take') of what comes back. The only meaningful gap is the absence of any sibling contrast for routing, which borders on being a usage-guideline rather than completeness issue.

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% and the single `calls` parameter already documents its 1–10 range and default of 5, so the schema carries the burden. The description adds only an indirect hint via 'route plan' and never mentions the calls count or what happens at the boundaries. Baseline 3 is appropriate.

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 concrete resource — the rep's day, mirroring the site's Today page — and enumerates its contents (follow-ups due, then surgeons with a reason to call across saved territories, own accounts, new-this-week first, each with a reason and next step). That is far more specific than a restatement of the name 'my_day'. It falls short of 5 because it never names or contrasts a sibling such as my_follow_ups, so an agent must infer the boundary itself.

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?

'Start a morning or a route plan here' does give a usage context, and the note about counting toward the plan's daily territories ties it to planning workflows. But there is no when-not guidance and no explicit alternative named, so the agent has to infer that my_follow_ups or my_territories cover narrower slices.

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