Skip to main content
Glama
elchin92

Avito MCP

by elchin92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Capabilities: what is enabled in this run

meta_capabilities
Read-onlyIdempotent

Retrieve machine-readable configuration of mode, allow/deny lists, confirmation, dry-run, and idempotency settings. Use it to verify available operations before calling tools.

Instructions

Returns a machine-readable description of the current configuration: mode, allow/deny lists, confirmation, dry-run, idempotency, local file access. Useful for an agent to understand which operations are fundamentally available before attempting to call tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
nameYes
toolsYes
accountYes
versionYes
featuresYes
moneyUnitsYes
schemaHashYes
approvalModeYes
dryRunDefaultYes
denyToolsCountYes
allowToolsCountYes
confirmationModeYes
idempotencyTtlSecYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.3.0
    • addedOutput schema / properties / account
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "namespace": {
+      "type": "string"
+    },
+    "profileId": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "profileId",
+    "namespace"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / approvalMode
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / features / properties / persistentState
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / features / properties / reusableHttpBroker
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / features / properties / sharedRateLimiter
      Added value: +{
+  "type": "boolean"
+}
    • changedOutput schema / properties / features / required
      Previous value: -[
-  "dryRun",
-  "idempotency",
-  "confirmation",
-  "hardConfirmation",
-  "fileUploads",
-  "sensitiveAuthTools"
-]New value: +[
+  "dryRun",
+  "idempotency",
+  "confirmation",
+  "hardConfirmation",
+  "fileUploads",
+  "sensitiveAuthTools",
+  "persistentState",
+  "sharedRateLimiter",
+  "reusableHttpBroker"
+]
    • addedOutput schema / properties / moneyUnits
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bbip": {
+      "type": "string"
+    },
+    "default": {
+      "type": "string"
+    },
+    "wallet": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "default",
+    "bbip",
+    "wallet"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / schemaHash
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / tools
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "available": {
+        "type": "boolean"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "environment": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "requiredScopes": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "risk": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "domain",
+      "risk",
+      "environment",
+      "available",
+      "requiredScopes"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "name",
-  "version",
-  "mode",
-  "allowToolsCount",
-  "denyToolsCount",
-  "features",
-  "confirmationMode",
-  "dryRunDefault",
-  "idempotencyTtlSec"
-]New value: +[
+  "name",
+  "version",
+  "schemaHash",
+  "mode",
+  "allowToolsCount",
+  "denyToolsCount",
+  "features",
+  "confirmationMode",
+  "approvalMode",
+  "dryRunDefault",
+  "idempotencyTtlSec",
+  "account",
+  "tools",
+  "moneyUnits"
+]
  2. First observedv0.7.4

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent; description adds value by detailing what configuration fields are returned (mode, allow/deny lists, etc.), complementing annotations.

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, front-loaded with core functionality, no wasted words.

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?

For a zero-parameter tool with annotations and output schema, description fully conveys purpose and usage context.

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

Parameters3/5

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

No parameters; schema description coverage is 100%, baseline applies. Description adds no parameter info, but none is needed.

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?

Clearly states it returns a machine-readable description of current configuration and lists specific items, distinguishing it from sibling meta tools like health or rate limits.

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?

Explicitly suggests using it to understand available operations before calling tools, but does not explicitly contrast with other meta tools.

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