Skip to main content
Glama

Niche of One Network

My account

my_account
Read-onlyIdempotent

Members. Show this member's Niche of One plan, renewal date and owned products. Never shows an email address or order number.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a genuinely useful behavioral constraint beyond that: it never returns an email address or order number, which tells the agent not to promise or hunt for those fields here. It does not say how identity is resolved (implicit auth context) or what happens for an unauthenticated/unknown member.

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?

Two sentences, both carrying content, with the privacy limitation placed last where it reads as a caveat. The opening fragment "Members." is a stray label that adds no information and slightly blunts the front-loading.

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 zero-argument read tool with full annotation coverage and no output schema, the description covers the returned fields at a useful granularity. The one omission is that it never states identity is taken from the session, which matters because the tool has no member identifier parameter.

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?

The tool takes zero parameters, so the baseline applies; the description correctly implies the member is derived from context rather than from input. No parameter meaning is missing because there are no parameters to document.

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?

"Show this member's Niche of One plan, renewal date and owned products" gives a specific verb plus three concrete resources, so an agent can tell this is an account-summary tool rather than a catalog or content reader. It stops short of naming a sibling such as plans_info, so the reader must infer the boundary between 'my plan' and general plan information.

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

Usage Guidelines3/5

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

Usage is only implied: "this member's" signals it is scoped to the authenticated caller, and the privacy clause hints that email/order lookups belong elsewhere. There is no explicit when-to-use or when-not-to-use statement, and no alternative is named for the excluded data.

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