Skip to main content
Glama
Sign In

AccountHub

by ai.accounthub
OverviewDiscussionsAdmin

upload_shared_project_file

Save an original file permanently to an AccountHub shared project (maximum 3 MiB), visible to every active member and their AI. Use only for files the user explicitly wants shared. Supply exactly one of content_base64 (small files only; filename required), attachment_id from your upload_attachment, or an explicit public URL fetched with SSRF protection. Local filesystem paths cannot be read remotely. Stored does not mean analyzed.

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": {
      "project_id": "<project_id>"
    },
    "name": "upload_shared_project_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
filenameNo
project_idYes
attachment_idNo
content_base64No

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say this is a non-destructive write; the description adds the real behavioral payload: permanence, a hard 3 MiB limit, visibility to all members and their AI, SSRF protection on URL fetches, and the caveat 'Stored does not mean analyzed' about downstream processing. That is substantial context the annotations do not carry.

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?

Five dense sentences, front-loaded with the action and limits, and every sentence carries information (each source option, the local-path exclusion, the analysis caveat). The density is high but there is no filler; only the brand prefix is mildly expendable.

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?

For a 5-parameter write tool with no output schema, it covers source selection, size limits, visibility, and security posture well enough to call correctly. It leaves the required project_id and the resulting file handle/identity unaddressed, which is a minor gap given no output schema exists.

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?

Schema coverage is 0%, so the description must compensate, and it does for the critical part: three mutually exclusive source parameters (content_base64, attachment_id, url) with the 'supply exactly one' constraint that the schema cannot express, plus the filename requirement for base64 and the SSRF caveat for url. project_id, the only required param, is left undescribed.

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 and resource ('Save an original file permanently to an AccountHub shared project') plus concrete scope: 3 MiB cap, visible to every active member and their AI. The shared-project destination implicitly separates it from direct-chat, Slack, and personal file tools in the sibling list.

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 use condition ('Use only for files the user explicitly wants shared') and rules out a whole class of input ('Local filesystem paths cannot be read remotely'), which steers the agent away from a common wrong invocation. It stops short of naming a specific alternative tool for the non-shared case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AccountHub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources