Skip to main content
Glama
Sign In
qune-tech/ocds-mcp

qune-tech/ocds-mcp

by qune-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

update_company_profile

Update company profile fields such as name, description, location, categories, or CPV codes. Changing the description triggers automatic re-embedding.

Instructions

Update a company profile. Only provided fields are changed. If the description changes, the profile is automatically re-embedded.

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": {
      "id": "<id>"
    },
    "name": "update_company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoriesNoNew procurement categories (replaces existing)
cpv_codesNoNew CPV codes (replaces existing)
descriptionNoNew description
idYesThe UUID of the company profile to update
locationNoNew location. Use empty string to clear.
nameNoNew company name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Discloses partial update behavior and that description changes trigger auto-re-embedding. However, no annotations exist, so the description carries the full burden; it lacks details on side effects, auth requirements, or idempotency.

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 sentences, no wasted words. The purpose is stated first, followed by a critical behavioral note. Efficient and front-loaded.

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

Completeness3/5

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

Adequate for basic functionality but lacks context on error handling (e.g., non-existent id), return value (no output schema), and any additional constraints. The re-embedding detail is a plus.

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%, but the description adds value by explaining partial update semantics and noting that empty string clears the location field. This goes beyond the schema's parameter descriptions.

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 clearly states 'Update a company profile' with the specific verb 'update' and resource 'company profile'. It distinguishes from sibling tools like create, delete, get, list.

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 explicit guidance on when to use this tool versus alternatives like create_company_profile or delete_company_profile. The phrase 'Only provided fields are changed' implies partial update but does not clarify prerequisites or scenarios.

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