Skip to main content
Glama

MedaRep

Lines I carry

my_lines
Read-onlyIdempotent

The companies the rep sells, each whole or narrowed to some brands, with the procedure families those brands cover. Other tools read these to mark switches won or lost, the rep's own recalls and their scorecard rows.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/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 genuine context beyond that: this is shared reference data that other tools consume, and it has a three-level shape (company → brand → procedure family). It still says nothing about volume, ordering, or what an empty result means.

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?

It is short and the resource description is front-loaded, but the second sentence is oblique — 'recalls' and 'their scorecard rows' are ambiguous without domain context, and describing who else reads the data is less useful than describing what the caller gets back.

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

Completeness3/5

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

With zero parameters and no output schema, the description carries the burden of explaining the return value, and it only sketches it (companies, brands, procedure families). For a simple read-only lookup that is workable, but the hierarchy's exact shape and whether one row or a nested tree comes back is left unstated.

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 no parameters, so there is no parameter semantics to explain and the schema is trivially complete. A baseline of 4 is appropriate; nothing in the description confuses the no-argument calling convention.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the resource's shape — companies the rep sells, narrowed to brands, with the procedure families those brands cover — which is more than the bare name 'my_lines' gives. But it is a noun phrase with no verb: it never says whether calling it returns this structure, and it does not distinguish itself from the obvious sibling set_my_lines.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-call guidance and no exclusion. The sentence about other tools reading these to mark switches, recalls, and scorecard rows describes downstream consumers, not the conditions under which an agent should invoke this tool rather than set_my_lines or my_accounts.

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