Skip to main content
Glama

Take My Repo

Read reviews

get_reviews
Read-only

Reviews written on Take My Repo by people who ran the project or model: rating, the machine they ran it on, and what worked or did not. An empty list means nobody has reviewed it yet, not that it is bad.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uid": "<uid>"
    },
    "name": "get_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesTake My Repo id: gh/{owner}/{repo} for GitHub, or hf/{model|space|dataset}/{id} for Hugging Face.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the empty-list case is explicitly disambiguated ('nobody has reviewed it yet, not that it is bad'), which prevents a common misreading of the result. It stops short of describing ordering, volume, or pagination.

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?

Two short sentences, front-loaded with what the tool returns and followed by the one interpretive caveat that matters. No filler or restatement of the name.

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?

With no output schema, the description carries the burden of describing return values and does so at a summary level (rating, machine, worked/did-not). For a single-parameter read tool with annotations covering safety, that is nearly complete; only result ordering or size is unaddressed.

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 uid parameter is fully documented in the schema, including the gh/ and hf/ id formats. The description adds nothing about the parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('Reviews written on Take My Repo by people who ran the project or model') and even enumerates the content of a review: rating, machine, and what worked or did not. No sibling in the list covers reviews, so no explicit differentiation is needed, but the description also never names the resource type (project vs. model) as a selector.

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 tool to call when it wants human feedback on a given uid. There is no statement of when to prefer it over get_resource or search, and no prerequisites or exclusions are given.

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