Skip to main content
Glama
CodeDreamer06

Unstop MCP Server

refresh_cache

Force an immediate refresh of cached hackathon data to ensure access to current event information.

Instructions

Force an immediate refresh of the cached open hackathon dataset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration for 'refresh_cache' in server.py.
    @server.tool(
        name="refresh_cache",
        description="Force an immediate refresh of the cached open hackathon dataset.",
    )
    def refresh_cache() -> dict:
        try:
            return service.refresh_cache().model_dump(mode="json")
        except (UnstopValidationError, UnstopAPIError, ValueError) as exc:
            raise ValueError(str(exc)) from exc
  • Core implementation of refresh_cache in the service class.
    def refresh_cache(self) -> CacheInfoResponse:
        self.build_cache(force=True)
        return self.get_cache_info()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a write operation ('refresh') but doesn't specify permissions, side effects, or performance impacts. No details on rate limits, success/failure responses, or data consistency are included, leaving significant gaps.

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 a single, efficient sentence with no wasted words, clearly front-loading the core action and resource. It's appropriately sized for a simple tool with no parameters.

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

Completeness2/5

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

Given the tool's mutation nature (implied by 'refresh'), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like what 'refresh' entails, potential downtime, or return values, making it inadequate for safe and effective use.

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 0 parameters, and the schema description coverage is 100%, so no parameter information is needed. The description appropriately avoids redundant details, aligning with the baseline for zero-parameter tools.

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 clearly states the action ('Force an immediate refresh') and the target resource ('cached open hackathon dataset'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its siblings like 'get_cache_info' or 'search_hackathons', which limits its differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives, such as when cached data is stale or needs updating. It lacks context on prerequisites, exclusions, or comparisons to sibling tools, leaving usage unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CodeDreamer06/UnstopMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server