Skip to main content
Glama
jehadbaniodeh

boq-mcp

by jehadbaniodeh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_project

Update project fields such as name, status, currency, or budget. Pass only the fields you want to change.

Instructions

Update a project. Pass only the fields you want to change.

status: draft|active|on_hold|completed|cancelled. currency: ILS|USD|EUR|JOD|SAR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
nameNo
descriptionNo
client_nameNo
locationNo
budgetNo
statusNo
currencyNo
report_languageNo
is_activeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / budget
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Budget"
+}
    • addedInput schema / properties / client_name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Client Name"
+}
    • addedInput schema / properties / currency
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Currency"
+}
    • addedInput schema / properties / description
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Description"
+}
    • removedInput schema / properties / fields
      Removed value: -{
-  "title": "Fields"
-}
    • addedInput schema / properties / is_active
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Is Active"
+}
    • addedInput schema / properties / location
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Location"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Name"
+}
    • addedInput schema / properties / report_language
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Report Language"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Status"
+}
    • changedInput schema / required
      Previous value: -[
-  "project_id",
-  "fields"
-]New value: +[
+  "project_id"
+]
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Without annotations, the description adds value by specifying allowed values for status and currency, and indicating partial updates. But it lacks details on side effects, authentication needs, or response behavior.

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?

The description is concise with two sentences and a list. Every sentence serves a purpose, though the list could be integrated into the schema as enums.

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 no annotations, no output schema, and 10 parameters, the description is incomplete. It lacks return value info, prerequisites, and tool relationships.

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

Parameters2/5

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

The description only covers status and currency among 10 parameters, providing allowed values. With 0% schema description coverage, it insufficiently documents the other parameters.

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?

The description states 'Update a project' which clearly identifies the verb and resource. It implies partial updates, distinguishing it from create_project and other tools.

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

Usage Guidelines3/5

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

The instruction 'Pass only the fields you want to change' provides some usage guidance. However, it does not explicitly state when to use this tool versus alternatives, or any prerequisites.

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