Skip to main content
Glama
concurrence-hq

forge-mcp

by concurrence-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

forge_metric_update

Update a metric's fields by providing its ID. Modify description, tags, additional notes, or service assignments, changing only the specified values.

Instructions

Update a metric. Only provided fields are changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags (alphanumeric keys and values, no hyphens or special characters)
org_idNoOrg ID (uses active org if omitted)
metric_idYesThe metric ID to update
descriptionNoUpdated description
additional_notesNoAdditional notes about the metric
applied_to_servicesNoService IDs this metric applies to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.14
    • removedInput schema / properties / additional_notes / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / additional_notes / type
      Added value: +[
+  "string",
+  "null"
+]
  2. First observedv0.1.13

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose partial-update semantics ('Only provided fields are changed'), which is useful, but it omits side effects, authorization requirements, error behavior, or response details. For a mutation tool this is a significant gap.

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?

Two short sentences with no filler. The purpose is front-loaded, and the patch behavior is communicated in a compact second sentence. Every word earns its place.

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?

For a mutation tool with six parameters, no annotations, and no output schema, this description is underspecified. It does not explain what happens when fields are omitted, what the response contains, or any prerequisites or side effects, leaving an agent with little context for correct invocation.

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%, so all six parameters already have descriptions. The description adds no parameter-specific detail beyond reinforcing the partial-update behavior, which is already implied by the schema's optional fields. The baseline of 3 is appropriate.

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 a specific action ('Update') on a specific resource ('a metric'), which distinguishes it from metric creation and other sibling update tools. However, it does not explicitly contrast itself with forge_metric_create or any other sibling, so it stops short of a 5.

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 given on when to use this tool versus alternatives such as forge_metric_create or other update tools. The only usage hint is the partial-update statement 'Only provided fields are changed,' which is behavioral rather than contextual.

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