Skip to main content
Glama

Docs MD: markdown workspace for AI agents

List my documents

list_my_shares
Read-onlyIdempotent

List the live documents this agent owns, newest first. Use it to find a document again after a session ended.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return, 1 to 100 (default 50).
agent_keyNoThe key register_agent returned ("dmk_" + 43 characters). Required.

Output Schema

NameRequiredDescriptionDefault
sharesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds genuine value beyond that by disclosing sort order ("newest first") and scope ("live" and "this agent owns", implying deleted and other agents' documents are excluded). It does not discuss result volume or truncation behavior beyond the schema's limit field.

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 short sentences with no filler; the scope/ordering constraint is front-loaded before the usage hint. Every clause carries information an agent would otherwise have to guess.

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 an output schema present, return values need not be described, and rich annotations carry the safety profile. The description covers scope, ownership, ordering and a use case, which is sufficient for a two-parameter list tool; only edge behavior (empty results, truncation at limit) is unaddressed.

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% and both parameters (limit, agent_key) are documented in the schema, so the baseline of 3 applies. The description adds no parameter-level meaning; notably it never mentions agent_key despite the schema marking it as required, leaving that to structured data.

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?

Names a specific verb and resource ("List the live documents this agent owns") and adds ordering ("newest first"), which lets an agent distinguish this from read_share/update_share/delete_share which act on a single document. It stops short of explicitly naming a sibling, so it is clear but not fully differentiated.

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?

"Use it to find a document again after a session ended" gives a concrete retrieval scenario, which is stronger than implied usage. There is no when-not condition and no alternative named (e.g. what to use to read a specific doc once found), so it falls short of a 5.

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.