Skip to main content
Glama

Report a Bug

report_bug

Tell the ShareWatch developers what this server got wrong. Use it for outright bugs — an unexpected error, a wrong result — and equally for friction: a confusing parameter, an unhelpful error message, a task that took three calls when it should have taken one. Your assessment of the API is the point; it is the only way its designers learn how it behaves in practice. The report is written to the user's own audit log, visible to them and to their workspace administrators, and to ShareWatch's operational logs. Write about the tool, never about the user's documents or conversation. Before filing, check that the behaviour is not one of these, which are by design and not bugs: (1) Google grants access per FILE — sharing a folder does not share its contents, and files inside appear only when shared themselves; (2) list_files and search_files see only what the user has shared, never their whole Drive; (3) Drive's Open With menu never grants Google Docs, Sheets or Slides — the picker does; (4) a file whose owner turned off download and copy for viewers cannot be read through any API — only its owner can change that; (5) get_status.available_tools lists what the server implements, not what this caller may use. If the user has one of these, explain it to them instead of reporting it; the docs at https://sharewatch.ai/docs.html cover each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYesThe tool that had the problem (e.g. 'update_document', 'read_file')
file_idNoThe file ID involved, if applicable
descriptionYesYOUR experience of using this tool — you are the one being asked, not the user. What you tried, what the API did instead, and what would have made it work. Opinions welcome: if a parameter is awkward, an error was unhelpful, two calls were needed where one should do, or the tool made a task harder than it should have been, say so plainly. Write about ShareWatch, not about the user's task: no document contents, no quoted text, no file or people names. Their material is not the subject and does not belong here. Maximum 2000 characters.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
whereYeswhere the report went, so the agent can tell the user where to look for it
loggedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only indicate the tool is not read-only, not idempotent, not open-world, and not destructive. The description adds meaningful behavioral context beyond those flags: reports are written to the user's audit log, visible to workspace administrators, and recorded in ShareWatch's operational logs. It also clarifies scope boundaries, telling the agent to write about the tool, not the user's documents or conversation.

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 description is longer than average, but it earns its length by front-loading the core purpose and then providing necessary exclusions and behavioral constraints. The five-item by-design list is verbose but valuable because it prevents misuse of the tool. It is well-organized and not redundant with the schema.

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?

The description is complete for a bug-report tool: it states what to report, when to report it, what not to report, where the report goes, scope limitations, and where to find supplementary documentation. The output schema likely covers the return value, so the description does not need to explain it. An agent has everything needed to invoke the tool correctly.

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 description coverage is 100%, so the schema already documents the tool, file_id, and description parameters well. The description reinforces the intent behind the description parameter (focus on the agent's experience, not user content), but it does not substantially add new semantic meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 opens with a concrete statement of purpose: 'Tell the ShareWatch developers what this server got wrong.' It clearly identifies the resource (ShareWatch's API/server behavior) and the action (reporting bugs and friction), and it is easily distinguished from sibling tools, which all perform file, document, or status operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description is explicit about when to use the tool: for outright bugs and for friction such as confusing parameters or unhelpful errors. It also gives a detailed when-not-to-use list of five by-design behaviors, instructing the agent to explain those to the user instead of reporting them. This is strong usage guidance with clear exclusions.

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.

Resources