Skip to main content
Glama

Attify

Your Attify account

get_my_account
Read-onlyIdempotent

Who is signed in, in which organization, and what kind it is: a vendor of an AI agent, a company that buys AI agents, or an investor. Says which signed-in tools answer for it. Needs sign-in to Attify; reads only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety bar is low. The description adds real value beyond them by disclosing the auth requirement and by telling the agent the response also names which signed-in tools answer for the account — an output behavior no annotation covers. Minor duplication in 'reads only' is the only shortfall.

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?

Front-loaded with identity/org first, then type taxonomy, then available tools, then the auth/read caveat — three short sentences plus a fragment, none wasted. No filler or restatement of the tool name.

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?

Since there is no output schema and no parameters, the description must carry the return-value burden, and it largely does: signer identity, organization, organization type, and answering tools. Slightly unclear whether it returns more fields (roles, plan, IDs), which keeps it short of a 5.

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?

Zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. It correctly spends no words on arguments.

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?

Names a specific resource ('who is signed in, in which organization') and adds the organization-type taxonomy (vendor/buyer-of-agents/investor), which is concrete enough to distinguish it from every sibling that fetches verdicts, evidence, or standards. It also states what the tool reports about tool availability, so its scope is unambiguous.

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?

States a prerequisite ('Needs sign-in to Attify') but never says when an agent should choose this over, say, asking 'ask_attify' or checking 'get_program_status'. Usage is only implied: an agent must infer it is for establishing identity/org context rather than for any analytical task.

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