Skip to main content
Glama
Sign In
Alcove

Alcove

Official
by OctopusGarage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

alcove_connector_github_stars_index

Indexes a GitHub Stars JSON export to organize and search your starred repositories using tags and workspace.

Instructions

Index a GitHub Stars JSON export.

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": {
      "export_file": "<export_file>"
    },
    "name": "alcove_connector_github_stars_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeNo
tagsNo
workspaceNo
export_fileYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are present, so the description must carry the burden of behavioral disclosure. It merely states 'Index' without explaining what happens (e.g., whether it's destructive, any permissions needed, or side effects). This is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is a single sentence and concise, it is too brief to convey necessary information. The structure lacks any breakdown or additional context, making it under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has multiple parameters and sibling tools, the description fails to provide enough context for an agent to correctly invoke it. It does not explain return values (despite having an output schema), parameter usage, or relationship to other tools.

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

Parameters1/5

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

The description adds no explanation for the four parameters. With 0% schema coverage, the agent must rely entirely on the parameter names (home, tags, workspace, export_file) which lack semantic meaning. No defaults or usage hints are provided.

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 action ('Index') and the specific resource ('a GitHub Stars JSON export'). It distinguishes itself from the sibling tool 'alcove_connector_github_stars_import_url' which handles URL imports, effectively narrowing the scope.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as the URL import sibling. The agent is left to infer context from the tool name alone, which is insufficient for proper tool selection.

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