Skip to main content
Glama
Sign In

Meridian

by ai.the-meridian
OverviewDiscussions(2)Admin

Update Feature

feature_update

Edits a Plan Builder feature's name or description. feature_id is the uuid or handle from features_list. The key and type are set at creation and cannot change: create another feature instead. Which plans grant the feature, and its value in each, is set with plan_update. Takes the app_id returned by apps_list. Returns the same shape as one features_list entry.

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": {
      "app_id": "<app_id>",
      "feature_id": "<feature_id>"
    },
    "name": "feature_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name.
app_idYesThe app uuid returned by `apps_list`.
feature_idYesFeature uuid or handle from `features_list`.
descriptionNoNew description. Pass null to clear it.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds real behavioral context beyond that: key and type cannot be changed, and the return value matches a features_list entry. It stops short of stating permission requirements or what happens on an invalid feature_id, which keeps it below a 5.

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?

Four tight sentences, front-loaded with the editable fields, then the immutability constraint, then the related-tool routing, then the return shape. No filler and nothing repeated.

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

Completeness5/5

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

For a five-parameter mutation with no output schema, the description covers the editable surface, the immutable surface, the alternative tool for related changes, and the return shape by reference to features_list. An agent has everything needed to call it correctly.

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 every parameter is already documented, and the description largely restates the schema's provenance notes for feature_id and app_id. It adds the useful constraint that key and type are not editable parameters, but that is marginal over the schema baseline.

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

Purpose5/5

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

States a specific verb and resource: edits a Plan Builder feature's name or description. It also scopes what is out of reach (key and type are immutable) and names the sibling that handles the related concern (plan_update for plan grants), so an agent can distinguish it from feature_create and plan_update without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says what to do instead when the immutable fields need changing ('create another feature instead') and routes plan-grant/value changes to plan_update. That is a clear when-to-use and when-not-to-use statement with a named alternative.

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

All Meridian toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources