Skip to main content
Glama

MedaRep

Follow-ups due

my_follow_ups
Read-onlyIdempotent

The rep's open follow-ups (and their team's), soonest first, overdue flagged; until (YYYY-MM-DD) limits them to what is due by then, e.g. the end of this week.

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

Input Schema

NameRequiredDescriptionDefault
untilNoOnly those due by this day, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds real behavioral detail beyond that: results include the team's follow-ups, are returned soonest-first, and overdue items are flagged. That is useful but short of rich disclosure — nothing about result volume or how team vs. personal items are distinguished.

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?

One front-loaded sentence with semicolon-separated clauses: scope and ordering first, then the parameter note. No filler and nothing redundant to trim.

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 single optional-parameter, read-only list tool with no output schema, the description covers scope, ordering, overdue signaling and the filter's meaning — enough to call it correctly. Output shape and approximate result volume remain unstated, which is the only meaningful gap.

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 description coverage is 100% and the single property already documents 'Only those due by this day, YYYY-MM-DD', so the schema carries the weight. The description restates the same semantics and only adds a use-case example ('the end of this week') plus a reminder that the cutoff is by due date rather than creation date.

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 identifies the resource precisely — the rep's open follow-ups plus their team's — and adds a sort order ('soonest first, overdue flagged'). It never states the verb explicitly (list/retrieve) and does not name the sibling set_follow_up as its write counterpart, but the scope is clear enough that an agent would not confuse it with a mutation tool.

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?

Usage is only implied: an agent can infer this is the read path for follow-ups, and the 'until' example ('e.g. the end of this week') hints at the common end-of-week use case. There is no explicit when-to-use/when-not statement and no alternatives named, so the routing guidance is thin.

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