Skip to main content
Glama

share_report

Destructive

Share one existing expense report with user-named recipients. No server preview: shares and emails on call. Default to reviewer: they can open and edit that report's Google Sheet, inspect receipts, comment, approve, or request changes, but cannot act for the owner or use accounting integrations. Use accountant only when the user explicitly asks for ongoing accounting access; it creates the established accountant relationship and broader report-management workflow.

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": {
      "reportId": "<reportId>",
      "recipients": "<recipients>"
    },
    "name": "share_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportIdYes
recipientsYes
recipientRoleNoUse reviewer for report-only approval. Use accountant only for explicit ongoing accountant access.reviewer

Output Schema

NameRequiredDescriptionDefault
messageYes
successYes
sharedWithYes
finalAnswerNo
recipientRoleYes
responseGuidanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / sharedWith / items / format
      Removed value: -"email"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "finalAnswer": {
      +      "type": "string"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "recipientRole": {
      +      "type": "string"
      +    },
      +    "responseGuidance": {
      +      "type": "string"
      +    },
      +    "sharedWith": {
      +      "items": {
      +        "format": "email",
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "message",
      +    "sharedWith",
      +    "recipientRole"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / recipientRole
      Added value: +{
      +  "default": "reviewer",
      +  "description": "Use reviewer for report-only approval. Use accountant only for explicit ongoing accountant access.",
      +  "enum": [
      +    "reviewer",
      +    "accountant"
      +  ],
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "description": "Standard ExpenseBot tool result envelope. `message` is the human-readable summary the AI cites; `data` is the structured payload (totals, breakdowns, ids, etc.). On failure, `success` is false and `error` carries a code/message/hint triple.",
      -  "properties": {
      -    "data": {
      -      "additionalProperties": true,
      -      "description": "Structured payload. Shape varies per tool — common keys: total, breakdown, comparison, sampleMeta, ids, expenseId, reportId, signupUrl, results.",
      -      "type": "object"
      -    },
      -    "error": {
      -      "additionalProperties": true,
      -      "description": "Present only when success === false.",
      -      "properties": {
      -        "code": {
      -          "type": "string"
      -        },
      -        "hint": {
      -          "type": "string"
      -        },
      -        "message": {
      -          "type": "string"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "message": {
      -      "description": "Human-readable result text. Always present on success; prefer rendering this verbatim before any further reasoning.",
      -      "type": "string"
      -    },
      -    "sampleMeta": {
      -      "additionalProperties": true,
      -      "description": "Set when the underlying dataset was truncated. isTruncated=true means the agent saw a sample of `sampleCount` of `totalCount` rows; aggregate totals are still accurate.",
      -      "properties": {
      -        "isTruncated": {
      -          "type": "boolean"
      -        },
      -        "sampleCount": {
      -          "type": "integer"
      -        },
      -        "totalCount": {
      -          "type": "integer"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "success": {
      -      "description": "False on tool errors; check before reading `data`.",
      -      "type": "boolean"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description adds genuinely useful context the annotations cannot convey: there is no server-side preview, and the share plus email fires immediately on call. It also enumerates the recipient's effective permissions (open/edit the Sheet, inspect receipts, comment, approve, request changes) versus the owner's retained powers. It stops short of saying whether existing shares are replaced or what happens on re-sharing the same recipient.

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?

Three sentences with the core action and its immediate side effect front-loaded, then role semantics. The middle sentence is long and list-heavy but every clause adds a permission distinction an agent could act on; minimal padding.

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?

With annotations and an output schema already supplied, the description carries only the parts structured fields cannot: immediate irreversibility (share + email on call, no preview) and the reviewer/accountant permission split. It is complete enough to call correctly, with the main residual gap being behavior on repeat shares or existing recipients.

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 only 33%, and the description compensates mostly on the one non-obvious parameter, recipientRole, by spelling out what reviewer access actually grants and what accountant access creates. The two required parameters, reportId and recipients, get no semantic elaboration beyond their names, and the enum's consequences are partly duplicated in the schema's own parameter description.

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?

States a specific verb and resource: 'Share one existing expense report with user-named recipients,' and clarifies scope ('one existing') plus the role dimension. It implicitly distinguishes itself from accounting-push siblings by noting the shared reviewer 'cannot ... use accounting integrations,' though it never names an alternative tool directly.

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 explicit selection guidance for the role parameter: default to reviewer, and use accountant 'only when the user explicitly asks for ongoing accounting access.' That is a strong when-to-use rule for the main decision point, but there is no guidance on when to pick this tool over siblings like send_report_to_accounting or export_report.

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.