Skip to main content
Glama
Sign In
Ambivo MCP Server

Ambivo MCP Server

Official
by ambivo-corp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_auth_token

Authenticate with the Ambivo API by providing a JWT bearer token. Required before using any other tools.

Instructions

Set the authentication token for API requests. This must be called before using other tools to authenticate with the Ambivo API.

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": {
      "token": "<token>"
    },
    "name": "set_auth_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesJWT Bearer token for authentication with Ambivo API

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior2/5

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

No annotations exist, so the description carries full burden. It only says 'Set' with no details on whether the token overwrites, persists, or if there are validation checks. This is minimal disclosure for a mutation tool.

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, each serving a purpose: action and usage context. No extraneous wording, efficient and direct.

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?

Given a simple tool with one parameter and no output schema, the description adequately covers the prerequisite nature and basic action. It could mention error behavior or state persistence, but overall it's sufficient.

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?

Schema coverage is 100% and the description mirrors the schema's description of 'JWT Bearer token'. It adds no new meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 the verb 'Set' and the resource 'authentication token for API requests', and specifies it must be called before other tools, distinguishing it from the sibling tool 'natural_query'.

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 explicitly states that this tool must be called before using other tools for authentication, providing clear context. No alternatives or exclusions are mentioned, but the prerequisite advice is strong enough for a 4.

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