Skip to main content
Glama

1Lookup

by io.1lookup
OverviewDiscussionsAdmin

Get account plan and credits

get_account
Read-onlyIdempotent

Get which 1Lookup account is connected, its plan, and its remaining credits. Free, spends no credits. Useful before a large run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoThe signed-in user, so the assistant can say which account it is using
usageNoLookups and credits consumed, this period and all time
tokensYesCredit balances, including total_available
organizationYesThe organization the credits belong to, by name
subscriptionNoCurrent plan, or null when there is no Stripe subscription

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / api_key
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Usage for the calling API key, empty for MCP callers",
-  "type": "object"
-}
    • changedOutput schema / properties / organization / description
      Previous value: -"The organization the credits belong to"New value: +"The organization the credits belong to, by name"
    • changedOutput schema / properties / user / description
      Previous value: -"The signed-in user"New value: +"The signed-in user, so the assistant can say which account it is using"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds genuinely new behavioral context: the call is free and consumes no credits, which matters for an agent deciding whether to check before a costly run. Good value beyond structured fields, though it doesn't discuss response specifics (covered by the output schema).

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?

Three short sentences, front-loaded with what it returns, followed by cost and intended timing. No filler.

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?

Zero parameters, full annotation coverage, and an output schema that documents return values. Combined with the description's cost and timing guidance, an agent has everything needed to call it correctly.

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 there is nothing for the description to disambiguate. Baseline 4 applies.

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 three concrete resources: connected account identity, plan, and remaining credits. This is clearly distinguishable from siblings like bulk_verify and verify_email, which perform lookups rather than account introspection.

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?

Gives a clear situational cue — 'Useful before a large run' — telling the agent when to call it. It stops short of naming explicit alternatives or stating when NOT to call it, so it falls just below the top band.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 1Lookup 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