Skip to main content
Glama
Sign In

MappaIQ

by com.mappaiq
OverviewDiscussions(1)Admin

List shares

get_shares
Read-only

Query sharing and access information. Use for questions like:

  • "What have I shared with Bob?" / "What can Bob see?"

  • "Who has access to the DFW Portfolio folder?"

  • "Under this folder I have 10 zones — tell me who each one is shared with"

  • "What layers does sarah@company.com have access to?"

  • "Who has admin access to anything?" Always use this tool when the user asks about sharing, access, permissions, or what someone can see. Provide either a person name/email OR a layer name (or both).

Input Schema

NameRequiredDescriptionDefault
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
layerNameNoLayer or folder name. Returns everyone who has been given access to it.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
personQueryNoName or partial email of a person to look up. E.g. 'Bob', 'sarah', 'smith@company.com'. Returns all layers this person has been shared with.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.
includeDescendantsNoWhen layerName is a folder, also report sharing for all child/grandchild layers inside it. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the constraint that either a person or a layer (or both) must be supplied, but says nothing about result shape, size limits, or how sharing entries are ordered/aggregated.

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?

Purpose is front-loaded in the first sentence, and the example bullets are concrete and each demonstrate a distinct query shape. The closing 'Always use this tool when...' sentence partly restates the bullet examples, adding mild redundancy.

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 read-only query with no output schema, the description covers purpose, when-to-use, and the person/layer input contract adequately. It leaves the shape of the returned access data unspecified, which is the one remaining gap an agent might care about.

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 all six parameters are already documented, including the conversation_id protocol and includeDescendants default. The description's 'person name/email OR a layer name (or both)' adds a small amount of disambiguation about how personQuery and layerName combine, but nothing beyond what the schema implies.

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 ('Query sharing and access information') and the five example questions pin down exactly what the tool returns. The sharing/access framing distinguishes it cleanly from sibling tools like get_layers or find_listings, none of which concern permissions.

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?

Explicitly states the trigger conditions ('Always use this tool when the user asks about sharing, access, permissions, or what someone can see') and shows representative phrasings. It does not name a when-not case or an alternative tool for adjacent questions, which keeps it just 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.

All MappaIQ 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