Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Update Monitored Company

update_monitored_company

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stageNo'active' or 'removed' (optional)
agent_idYesID of the agent
identifierYesThe company's display name or domain.
data_updatesNoDict to merge into existing data (optional)
on_behalf_ofNoAn agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}
    • changedInput schema / properties / stage / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "active",
-      "removed"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "active",
+      "removed"
+    ],
+    "title": "Stage",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "ID of the agent",
+  "type": "integer"
+}
    • removedInput schema / properties / task_id
      Removed value: -{
-  "description": "ID of the task",
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "task_id",
-  "identifier"
-]New value: +[
+  "agent_id",
+  "identifier"
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description is not carrying the safety burden. It nevertheless adds real behavioral context beyond the annotations: the nightly-sweep side effect of setting stage='removed' versus resuming with 'active'. It does not disclose merge/replace semantics for data_updates, which is the remaining gap.

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?

Two tightly-scoped sentences inside a <summary> tag, with the primary action front-loaded and the stage semantics immediately after. The <returns> block is slightly redundant given the trivial return type, but nothing is padded.

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?

With no output schema at all, the description correctly supplies the return shape ('Dict with the updated company details'). Combined with schema-documented params and the sweep-behavior note, an agent has enough to call this correctly, though the authorizing context of on_behalf_of is left entirely to the schema.

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 description coverage is 100%, so the baseline is 3, but the description earns an extra point by explaining the consequence of each stage value rather than just echoing the enum. It still says nothing beyond the schema about data_updates or on_behalf_of.

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?

The first sentence names a specific verb (Update) and resource (a single monitored company) plus the two mutable facets (stage and/or data), which separates it from query_monitored_companies and track_monitored_companies. It stops short of explicitly naming a sibling it is not, so a 4 rather than a 5.

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?

It gives concrete operational guidance for the stage parameter: 'removed' stops the nightly sweep, 'active' resumes it. That tells the agent when each value is appropriate, but it offers no guidance on when to use this tool versus track_monitored_companies or edit_monitor_members.

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

All Sliq 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