Skip to main content
Glama

get_my_ratings

Read-only

The coach's own client ratings/reviews (public ones only — a client can mark theirs private), newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: results are filtered to public reviews only (clients may mark theirs private) and ordered newest first, which an agent would otherwise not know. It stops short of describing volume, pagination, or what happens when the coach has no ratings.

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?

A single compact sentence with the filtering caveat and sort order front-loaded after the possessive scope. Nothing is padded, though the parenthetical sits mid-sentence where it interrupts the resource description.

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 simple authenticated read with no nested objects, the description covers scope, filtering, and ordering adequately, and the absence of an output schema is a minor gap since the resource (rating entries) is named. The only real hole is the undocumented limit parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter (limit) with 0% schema description coverage, and the description never mentions it. The schema bounds it to 1-100, but an agent gets no description-level guidance on what the limit caps or how it interacts with the 'newest first' ordering.

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?

Specific resource ('the coach's own client ratings/reviews') with implied list verb and a clear scope qualifier. It implicitly distinguishes itself from the sibling get_my_rating_summary by returning the individual entries rather than an aggregate, though it never states that contrast explicitly.

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 — a coach reviewing their own feedback — with no explicit when-to-use statement and no named alternative such as get_my_rating_summary for aggregated numbers. An agent can infer the purpose but must guess at the boundary with the summary sibling.

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.