Skip to main content
Glama

ContentSweep Supplier Feeds

approve_supplier_feed_profile

Persist an explicit approval of the exact profile after the operator has resolved its field meanings and rules.

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": {
      "profile_id": "<profile_id>",
      "expected_profile_hash": "<expected_profile_hash>",
      "approve": "<approve>"
    },
    "name": "approve_supplier_feed_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
approveYes
profile_idYes
expected_profile_hashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive mutation, so the description only needs to add context. It adds the sequencing precondition, but says nothing about whether approval is reversible, what state change results, or why a retry (idempotentHint=false) matters. Given the tool name and annotations, the description contributes modest extra value rather than none.

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?

A single front-loaded sentence with no filler; the precondition is attached to the action rather than buried later. The clause 'resolved its field meanings and rules' is slightly opaque, costing a bit of immediate comprehension.

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 three required, fully undocumented parameters and no output schema, the description should explain the hash contract and the meaning of the approve flag. It covers only the sequencing precondition, leaving the mechanics of a correct call — the most likely failure mode here — unaddressed.

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?

Schema description coverage is 0% across all three required parameters, so the description must carry the burden and it does not: profile_id, the approve boolean, and especially expected_profile_hash (plainly an optimistic-concurrency guard) go entirely unexplained. The phrase 'the exact profile' is the only faint gesture toward the hash, which is insufficient for a required argument whose misuse would cause call failures.

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?

Names a specific verb ('persist an explicit approval') and a specific resource (the supplier feed profile), and the act of approving is distinguishable from the create/delete/get/list siblings. It stops short of explicitly contrasting itself with the other profile tools, but the purpose is unambiguous.

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?

Supplies one real precondition: the operator must have already resolved the profile's field meanings and rules before calling. It never says what to do if that precondition is unmet, whether approval can be reverted (delete_supplier_feed_profile?), or how it relates to start_supplier_import, so the routing guidance is implied rather than explicit.

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.