Skip to main content
Glama
Sign In
MCP Advbox Server

MCP Advbox Server

by JonasSousaAP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

advbox_get_settings

Retrieve Advbox account settings and configuration for AI agents managing legal operations, clients, lawsuits, tasks, and financial transactions.

Instructions

Get Advbox account settings and configuration

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "advbox_get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It indicates a read operation ('Get') but does not state side effects, return format, authentication requirements, or rate limits. The minimal description adds little beyond the basic verb, leaving the agent without key behavioral context.

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?

The description is a single six-word sentence, 'Get Advbox account settings and configuration.' It is extremely concise, front-loaded, and contains no unnecessary words, every word earning its place.

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?

For a zero-parameter tool with a straightforward getter purpose, the description adequately states the core function. However, there is no output schema and the description does not explain what the returned settings look like or any operational context, making it complete enough for simple use but not deeply informative.

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?

The input schema has zero parameters, so schema description coverage is 100%. With no parameters, the description has no parameter semantics to add, and the baseline of 4 applies because there is nothing to clarify.

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 states a clear verb ('Get') and resource ('Advbox account settings and configuration'), making the tool's purpose unambiguous. It also distinguishes from sibling tools like advbox_list_customers and advbox_get_customer, which target different resources.

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?

The description offers no explicit guidance on when to use this tool versus alternatives, but the tool name and description strongly imply it is the go-to tool for retrieving account settings. Since no sibling tool covers settings, the usage context is implied rather than explicitly stated.

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