Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_theme

Add a project theme by specifying its name and whether it is AI-generated, along with optional description and confidence score.

Instructions

Add project theme

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": {
      "name": "<name>",
      "ai_generated": "<ai_generated>"
    },
    "name": "add_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTheme name
descriptionNoTheme description
ai_generatedYesTrue if AI-generated, False if user-created
confidence_scoreNoConfidence score 0-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

C2.2/5.0
Behavior2/5

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

The description adds no behavioral context beyond what annotations already imply (non-read-only, non-destructive). It does not disclose whether duplicate names are allowed, what side effects occur, or any error conditions.

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?

The description is a single short sentence, but it is under-specified and fails to convey meaningful information. While concise, it does not earn its place due to lack of substance.

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 has 4 parameters, no output schema, and minimal annotations, the description is severely lacking. It explains neither the purpose of a theme nor the effect of adding one, leaving the agent without sufficient context for correct use.

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 description coverage is 100%, so baseline is 3. The description contributes no additional context about parameters beyond the schema's existing descriptions, but does not contradict them either.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description 'Add project theme' merely restates the tool name with 'project' added. It lacks any explanation of what a 'theme' represents or how it differs from other add resources. Siblings like add_task, add_module, add_note are not differentiated.

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. There is no mention of prerequisites, when not to use it, or how it relates to sibling tools like update_theme or delete_theme.

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