Skip to main content
Glama

update_sidequest

Idempotent

Update a sidequest's name, status, priority, paused task, description, or flow IDs by providing the sidequest ID and desired changes.

Instructions

Update sidequest metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSidequest ID
nameNoNew name (NULL = don't update)
paused_task_idNoNew paused task ID (NULL = don't update)
paused_subtask_idNoNew paused subtask ID (NULL = don't update)
statusNo'pending', 'in_progress', 'completed', 'blocked' (NULL = don't update)
descriptionNoNew description (NULL = don't update)
flow_idsNoArray of flow IDs (NULL = don't update)
priorityNo'low', 'medium', 'high', 'critical' (NULL = don't update)
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the description's generic 'Update' adds no new behavioral insights. It does not contradict annotations.

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?

A single, concise sentence that directly states the purpose. It is front-loaded, but could arguably include more useful context without being verbose.

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

Completeness3/5

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

Given the 8 parameters and absence of output schema, the description is minimal. The schema covers parameters well, but the description lacks context on what 'metadata' encompasses, which is partially mitigated by schema completeness.

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?

With 100% schema coverage, the baseline is 3. The description does not add any meaning beyond the schema's parameter descriptions, which are already detailed.

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 'Update sidequest metadata' clearly specifies a verb and resource, but it does not distinguish this tool from many sibling 'update_' tools. It lacks specificity on what metadata fields are included.

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 on when to use this tool versus alternatives like update_task or update_subtask. No prerequisites or context provided, leaving the agent to infer usage from the name alone.

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/aryanduntley/aimfp'

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