Skip to main content
Glama

get_me

Read-onlyIdempotent

Returns who is signed in and every company they can open, with their role in each. This is the first call a client makes after sign-in: almost every other call needs a company id from companies[].id.

Any signed-in person may call it. It also does housekeeping on the way: it makes sure the person's personal company exists and turns any email invitations waiting for them into memberships, so a company someone was just added to shows up here.

The x-company-id header is optional here. currentCompanyId tells you which company the server will use for requests that send this header; with no header, or one naming a company the person is not in, it falls back to their personal company instead of failing.

Other fields: companyLimit is how many companies a person may create (null means no limit) and companiesCreated is how many they have created so far, for a "New company" button. onboardedAt on each company is null until its setup is finished. paused on each company lists what a Liliphant admin has stopped there because it costs money (recording, processing, ask, automations); empty means nothing is, and ask means AI answers are refused, so a screen can say so instead of offering them. operator is true for the people who may open the admin panel. logoUrl and brandColor appear on a company whose profile has a website that Things of Brand knows; both are left out otherwise. hasMeetings is true once the current company has at least one meeting (one still being processed counts); until then the app shows only the first-meeting screen and Settings.

Errors: 401 NOT_SIGNED_IN when no token is sent; 401 SESSION_EXPIRED when the token is no longer valid. GET https://meet-analyzer-api.50agents.com/api/v1/ui/me

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_me"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With annotations already declaring readOnly/idempotent/non-destructive/closed-world, the description goes well beyond them: it discloses housekeeping side effects (creating the personal company, converting pending email invitations into memberships), that any signed-in person may call it, and the two 401 error codes. The disclosed lazy-init side effects sit in slight tension with readOnlyHint, but they are user-owned, non-destructive, and openly stated rather than contradicted.

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 and call-order are front-loaded in the first two paragraphs, which is the right structure. The later field-by-field enumeration is dense and drifts into UI-copy rationale ("for a 'New company' button", "so a screen can say so") that an agent does not strictly need, keeping it short of a 5.

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?

For a zero-parameter, no-output-schema bootstrap call, the description covers identity, company list, role, header semantics, fallback behavior, field meanings, and error conditions. Nothing an agent needs in order to call it correctly or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero schema properties, so the baseline is 4, but the description adds real meaning beyond the empty schema by explaining the out-of-schema x-company-id header and the server's fallback rule. It also disambiguates response fields that have no output schema to document them (companyLimit vs companiesCreated, paused, onboardedAt, hasMeetings).

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?

The first sentence gives a specific verb and resource ("Returns who is signed in and every company they can open, with their role in each") plus the scope of the returned set. It also positions itself against the sibling tools, which are all docs/raw-API helpers, by describing itself as the identity/company bootstrap call.

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

Usage Guidelines5/5

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

"This is the first call a client makes after sign-in: almost every other call needs a company id from companies[].id" tells the agent exactly when to call it and why it precedes everything else. It also covers the conditional case for the x-company-id header, including the fallback when the header is absent or names a company the user is not in.

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