Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_theme

Idempotent

Update a theme's metadata including name, description, and confidence score by specifying the theme ID.

Instructions

Update theme metadata

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": {
      "theme_id": "<theme_id>"
    },
    "name": "update_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_idYesTheme ID to update
nameNoNew name (NULL = don't update)
descriptionNoNew description (NULL = don't update)
confidence_scoreNoNew confidence score (NULL = don't update)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds no further behavioral context, such as confirmation requirements, side effects, or the fact that it only updates specified fields while leaving others unchanged.

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

Conciseness3/5

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

At three words, the description is very concise but does not provide sufficient context for a tool with 4 parameters. It avoids fluff but sacrifices informativeness.

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?

The description lacks details on success/failure behavior, potential constraints (e.g., cannot update theme_id), or any return information. Given the complexity of update operations and lack of output schema, it is incomplete.

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?

Schema coverage is 100% with descriptive parameter descriptions (e.g., 'NULL = don't update'). The description does not add any meaning beyond the schema, meeting the baseline of 3.

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 theme metadata' clearly indicates a verb-resource pair, and combined with the parameter names (name, description, confidence_score), it specifies what is updated. It distinguishes from siblings like add_theme (create) and delete_theme (remove).

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 like add_theme, delete_theme, or other update tools. No context about prerequisites or conditions.

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