Skip to main content
Glama
Sign In
gh-autostar

gh-autostar

by Yolgz-sys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_recent_stars

Lists recent auto-star audit records with timestamp, repository, source, and reason so you can review which GitHub repos your agent starred and verify or reverse each action.

Instructions

列出最近的点星记录（审计用），包含时间、仓库、来源与原因。

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

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数，默认 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It partially compensates by disclosing the record fields returned (time, repository, source, reason), but it never defines what 'recent' means, what the ordering is, whether results are paginated, or what access is required. Adequate but with real behavioral gaps for a tool with zero annotation coverage.

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 sentence, front-loaded with the action and the returned fields, with zero filler. The parenthetical use-case is the only elaboration and it earns its place.

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?

For a one-optional-parameter read tool with no output schema, the description usefully enumerates returned fields, but leaves the recency window and sort order undefined, which matter for interpreting a 'recent' list. Complete enough to call, not complete enough to predict results.

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 coverage is 100% and the single 'limit' parameter is fully documented in the schema (min 1, max 50, default 10). The description adds no meaning about the limit or result ordering, so the schema does all the work; 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?

The description names a specific verb+resource ('list recent star records') and adds a stated purpose ('for auditing') plus the fields returned (time, repository, source, reason). An agent can tell this is a read-only history view rather than a per-repo status check like star_status, though no sibling is named 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?

The parenthetical 'for auditing' implies the usage context but gives no explicit when-to-use/when-not guidance and does not point to alternatives such as check_star or star_status for single-repo lookups. Usage must be inferred from the purpose phrase.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools