Skip to main content
Glama
demeet2k

Athena MCP Server

by demeet2k

athena_agent_refresh

Refresh agent boot state and message board projection, preserving coordination intent. New work coordinates enable automatic claiming; observer sessions remain read-only unless promoted.

Instructions

Refresh AGENT_BOOT_V1 and its Message Board projection. Existing session coordination intent is preserved; new explicit work coordinates activate AUTO claiming, while observer sessions remain read-only unless promoted deliberately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNo
fetchNo
remoteNo
profileNo
targetsNo
agent_idNo
work_keyNo
issue_repoNo
session_idNo
source_refNo
issue_limitNo
lease_secondsNo
prior_addressNo
coordination_modeNo
replication_reasonNo
shared_remote_modeNo
continuation_loop_idNo
coordination_detailsNo
coordination_claim_modeNo
continuation_shared_remote_modeNo
Behavior3/5

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

The description reveals useful behavioral traits about coordination mode handling (preserving existing intent, AUTO claiming activation, read-only observers). However, since no annotations are provided, it should also disclose side effects, permissions, or return format; the impact of 'refresh' on existing data is not explicitly stated.

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

Conciseness4/5

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

The description is concise and to the point, with no fluff. It front-loads the core function and adds a relevant nuance in the second sentence. However, given the tool's complexity, it could be better structured to include more detail without becoming verbose.

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?

With 20 parameters, no annotations, no output schema, and no parameter explanations, the description is severely incomplete. It fails to explain any parameter semantics, expected inputs, or result behavior, leaving an agent unable to correctly construct a call beyond guessing from parameter names.

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 provides no information about any of the 20 parameters, and the schema has no per-parameter descriptions. The parameter names like task, fetch, and remote are not self-explanatory in context, and the description fails to compensate for zero schema description coverage.

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 tool refreshes AGENT_BOOT_V1 and its Message Board projection, using a specific verb and resource. It doesn't explicitly distinguish from sibling tools or mention alternatives, so it's clear but not fully differentiating.

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 explicit guidance on when to use this tool vs alternatives. The description explains behavior but doesn't provide context for selecting it over other athena_* tools, or conditions that warrant a refresh. It leaves the agent to infer usage solely from the tool name and the action described.

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/demeet2k/athena-mcp-server'

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