Skip to main content
Glama
Sign In
github-stars-mcp

github-stars-mcp

by ENFernandes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

refresh_stars

Force a complete re-fetch of your GitHub starred repositories from the API to update the local database. Use when you need a fresh copy without relying on automatic checks.

Instructions

Force a full re-fetch of your starred repos from the GitHub API and update the local database. Read tools already check for updates automatically on use.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the key behavior: forcing a full re-fetch and updating the local database. However, it does not mention rate limits, whether the update is destructive, or failure behavior, leaving some gaps for a mutation-like operation.

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 concise sentences, with no wasted words. The first states the action, the second gives context, making it effective and well-structured.

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 zero-parameter tool, the description covers the main purpose and usage context. It could mention return values or potential side effects, but the refresh action is self-explanatory enough that the description feels complete.

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

Parameters4/5

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

The tool has zero parameters, so the baseline is 4. The description does not need to explain parameters, and the empty schema fully covers the input contract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action: 'Force a full re-fetch of your starred repos from the GitHub API and update the local database.' It uses a specific verb and resource, and the mention that read tools check automatically distinguishes its purpose from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides useful context by stating 'Read tools already check for updates automatically on use,' implying this tool is for forcing a manual refresh. It does not explicitly list alternatives or exclusions, but the context is clear enough to guide usage.

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