Skip to main content
Glama

Lovie Company Formation

Get Company Auto Post Ceiling

transaction_get_company_auto_post_ceiling
Read-only

Read the largest amount any of a company's categorization rules may post without a person reviewing it, when the rule sets no ceiling of its own. Empty means no company ceiling. A rule that names its own ceiling — including one deliberately without any — is not governed by this. Read-only.

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": {
      "companyId": "<companyId>"
    },
    "name": "transaction_get_company_auto_post_ceiling"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
enrollmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the closing 'Read-only' is largely redundant. The description does add genuine domain behavior: the fallback/precedence semantics and the interpretation of an empty result as 'no company ceiling.'

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?

The core definition is front-loaded and the sentences are dense and information-bearing, with no padding. The trailing 'Read-only' duplicates the annotations and the exclusion clause is slightly convoluted, but overall the length matches the concept.

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?

An output schema exists, so return values need not be explained, and the description still adds the one thing an agent needs to interpret them (empty = no ceiling). For a single-parameter read tool with full annotation coverage, nothing required to call it correctly is missing.

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?

Only one parameter (companyId) with 100% schema description coverage, so the schema does the work and the baseline is 3. The description adds no format, scoping, or lookup guidance for the UUID beyond what the schema states.

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?

States a specific verb (read) and a precisely defined resource: the company-level auto-post ceiling that applies only when a rule sets no ceiling of its own. It even scopes out the conceptually adjacent case (rules that name their own ceiling), so an agent can distinguish this from rule-level ceiling concepts without opening another schema.

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?

Gives an explicit condition of applicability — a rule with its own ceiling, including a deliberately empty one, is not governed by this. That is clear usage context, though it never names a sibling tool to use instead (e.g. the rule-level getter), so routing between related tools is still partly inferred.

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.