Skip to main content
Glama

MeshArc

by dev.mesharc
OverviewDiscussionsAdmin

Update a project's settings

update_project
DestructiveIdempotent

Change an existing project's name, schedule or settings. Only what you pass changes: in config only the keys given are replaced, the rest stay; a replaced value is not kept. Call get_project first to see the current values, and describe_project_config for valid keys; to start a different site use create_project instead. Nothing is fetched and no credits are spent now; the next run uses the new settings, and a settings change that alters how pages are read starts a fresh comparison baseline. Returns the updated project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoA new name; omit to leave it.
configNoSettings to change, e.g. {"max_pages": 200}; keys not given keep their values. Omit to leave them all.
scheduleNoA new schedule; omit to leave it.
project_idYesThe project's id, as list_projects or create_project returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / config / description
      Added value: +"Settings to change, e.g. {\"max_pages\": 200}; keys not given keep their values. Omit to leave them all."
    • addedInput schema / properties / name / description
      Added value: +"A new name; omit to leave it."
    • addedInput schema / properties / project_id / description
      Added value: +"The project's id, as list_projects or create_project returns it."
    • changedInput schema / properties / schedule / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "manual",
+      "hourly",
+      "daily",
+      "weekly"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / schedule / description
      Added value: +"A new schedule; omit to leave it."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=true): it discloses merge semantics ('only the keys given are replaced, the rest stay; a replaced value is not kept'), cost behavior ('no credits are spent now'), deferred effect ('the next run uses the new settings'), and a side effect ('starts a fresh comparison baseline'). These are exactly the traits an agent needs and the annotations do not convey.

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

Conciseness4/5

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

Front-loads the core action and then layers constraints in a single dense paragraph; every clause earns its place. It is slightly packed with stacked semicolons, which costs a little readability but not substance.

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?

No output schema, but the description states 'Returns the updated project.' Combined with the merge/cost/baseline behavior, everything needed to call this mutation tool correctly is present.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description still adds the overwrite nuance ('a replaced value is not kept') and points to describe_project_config for valid config keys, which the schema does not say. That is real added meaning, though most per-parameter detail is already in the schema.

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 (Change) and resource (existing project's name, schedule or settings), and explicitly scopes it against siblings: 'to start a different site use create_project instead' and 'Call get_project first'. An agent can distinguish this from create_project and get_project 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?

Gives explicit prerequisites ('Call get_project first to see the current values, and describe_project_config for valid keys') and names the alternative with its selecting condition ('to start a different site use create_project instead'). When-to-use and when-not-to-use are both covered.

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

All MeshArc toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources