Skip to main content
Glama

update_project_metadata

Update a project's surfaces and git remotes: a list you send replaces that whole list, omit a list to keep it, include id to keep an item. A surface sent without its id is treated as a new surface and the old one is deleted, dropping its epic/task links — always send the id when renaming. Surfaces reference remotes by remoteUrl (auto-added to remotes). Never send local folder paths. If the user is working inside a VSCode workspace and a <workspace>/.bilg/bilg.config.json exists, prefer that file's projectName over the API key's default project.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_project_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
remotesNo
surfacesNo
projectNameNoDefaults to the API key's default project
expectedUpdatedAtNoupdatedAt from get_project_metadata; mismatch fails with metadata_conflict. null means never set, and is then the right value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so for the most important trait: it discloses that a surface sent without `id` deletes the old surface and drops its epic/task links, and that `remoteUrl` gets auto-added to remotes. It stops short of permissions, atomicity, or what happens to other metadata on failure.

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?

Five dense sentences, each carrying a distinct rule, with the list-replacement contract front-loaded before the destructive edge case. No filler and no restatement of the tool name.

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

Completeness4/5

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

For a 4-param mutation tool with no annotations and no output schema, the description covers replacement semantics, the destructive pitfall, path restrictions, and project resolution. It does not describe the success response shape or the effect of concurrent updates beyond the schema-documented metadata_conflict.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, so the description must compensate and does: it explains list-replacement semantics versus the schema's per-item `id` hint, the coupling between `remoteUrl` and `remotes`, the prohibition on local folder paths, and the workspace-config override for `projectName`. That is meaningful semantics the schema cannot express.

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?

Names a specific verb and two concrete resources ('Update a project's surfaces and git remotes'), immediately distinguishing it from the read-only sibling get_project_metadata. An agent knows exactly what domain object this mutates without opening the schema.

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

Usage Guidelines4/5

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

Gives strong conditional rules: omit a list to keep it, include `id` to keep an item, always send `id` when renaming, use the workspace `.bilg/bilg.config.json` projectName when present. It never names a sibling tool as an alternative, so routing is implied rather than explicit, but the when-to-do-what guidance is unusually concrete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources