Skip to main content
Glama

Best of Go

Star history

star_history
Read-onlyIdempotent

The stars one repo gained in each week, month, or year since it was created, oldest first.

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": {
      "repo": "<repo>"
    },
    "name": "star_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesThe repo as owner/name, such as pressly/goose.
bucketNoOne of week, month, or year. Default month.

Output Schema

NameRequiredDescriptionDefault
repoYes
bucketYes
pointsYes

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 idempotentHint, so the description doesn't need to establish safety, and it usefully adds behavior the annotations don't: results are aggregated per week/month/year and returned chronologically 'oldest first'. It stops short of saying whether empty buckets appear or how large the series can get, but the added ordering and aggregation semantics are real value.

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?

A single compact sentence that front-loads the returned quantity and closes with the ordering guarantee. Every phrase earns its place, with no boilerplate or redundancy.

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 two-parameter read-only tool with a full output schema and complete parameter documentation, the description covers the essentials: what is counted, the bucket granularity, the time span, and the sort order. The only residual gap is series edge cases such as zero-star periods, which is minor given the output schema.

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 description's mention of week/month/year only restates the bucket values already documented in the schema, with no added detail on default behavior beyond what the schema says. The baseline 3 is appropriate when the schema carries the parameter semantics.

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 a specific resource (a repo's star count per time bucket) and states the aggregation granularity and ordering, so an agent can tell it returns a time series rather than a point-in-time count. It does not differentiate itself from siblings such as get_repo, which likely also reports a total star count, leaving the distinction to be inferred.

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: the words 'history' and 'since it was created' suggest looking up growth trends rather than current stats, but there is no explicit when-to-use, when-not-to-use, or pointer to get_repo for a simple current count. No prerequisites or limits are stated.

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