Skip to main content
Glama
Sign In
gh-autostar

gh-autostar

by Yolgz-sys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

check_star

Checks if a GitHub repository is already starred by the current account by comparing GitHub remote status with the local ledger; read-only.

Instructions

查询某个 GitHub 仓库当前是否已被当前账号点星（同时检查 GitHub 远端与本地账本）。只读操作。

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

Input Schema

NameRequiredDescriptionDefault
repoYes仓库引用，如 owner/repo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses that the operation is read-only and checks two sources, the GitHub remote and the local ledger, but it does not explain authentication requirements, rate limits, or how discrepancies between the two sources are handled. That is useful context, but not complete behavioral disclosure.

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?

The description is two compact sentences with no wasted wording. The primary purpose is front-loaded, and the remote-plus-ledger scope and read-only nature follow immediately.

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?

This is a simple one-parameter read-only check, and the description covers what is checked and from which sources. It would be more complete if it stated the return value, such as a boolean or status object, especially since no output schema exists. Given the low complexity, that is a minor gap rather than a blocking one.

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?

There is one parameter with 100% schema description coverage, so the schema already documents the `repo` parameter and provides the `owner/repo` example. The description adds no further parameter semantics, such as accepted formats or case sensitivity. A baseline of 3 is appropriate when the schema already does the heavy lifting.

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 states a specific verb and resource: check whether a given GitHub repository is currently starred by the current account. It adds useful scope detail by noting that both the GitHub remote and the local ledger are checked. It does not differentiate this tool from the sibling `star_status`, which appears to have an overlapping purpose.

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 description implies when to use the tool: when you need the current starred state for one repository. It does not explicitly say when to prefer it over `star_status`, nor does it state any exclusions or prerequisites. The read-only note helps, but there is no direct routing guidance.

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