Skip to main content
Glama

Get Authorized Shares

get_company_authorized_shares
Read-only

Returns a C-Corp's authorized shares (noOfShares) and par value per share (shareValue, in US dollars), as the Company page of the doola dashboard shows them. For an LLC it says shares do not apply. Answer in plain language and never show the user the field names.

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": "get_company_authorized_shares"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: values are in US dollars, they mirror the dashboard's Company page presentation, and LLCs return a 'not applicable' result rather than an error. It does not discuss empty/missing data for unformed companies, keeping it below 5.

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 plus a formatting directive, with the return payload front-loaded before the LLC edge case and the presentation rule. No filler; the parenthetical field names exist to help the agent map to data, not to pad.

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?

With no output schema, the description carries the burden of describing return values, and it does so explicitly: two named fields, currency units, dashboard parity, and the LLC branch. For a simple two-value read tool, an agent has everything needed to call it and present the result.

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?

All three parameters are optional analytics metadata and the schema description coverage is 100%, so the schema fully documents them. The description adds nothing about context, llm_model, or conversation_id, which is acceptable here but earns only the baseline.

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?

Uses a specific verb ('Returns') with a precisely bounded resource: authorized shares (noOfShares) and par value per share (shareValue, USD), anchored to the doola dashboard's Company page. That narrow scope effectively separates it from the other get_company_* tools, but the description never names or contrasts a sibling, so it stops short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implicitly tells the agent this tool applies to C-Corps and that LLCs get a 'shares do not apply' answer, which is useful entity-conditioned guidance. However, there is no explicit when-to-use statement, no mention of alternatives such as get_company_formation_details, and no exclusion conditions beyond the entity type.

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.