Skip to main content
Glama

Get profile attributes

get_profile_attributes
Read-onlyIdempotent

The business's current Google attributes plus every attribute Google offers for its primary category (id, display name, group, value type and allowed values). Use these names with request_profile_update field 'attributes'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile_id": "<profile_id>"
    },
    "name": "get_profile_attributes"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral content by clarifying the response is a union of current values and the category's allowed attribute set, but it says nothing about permissions, scoping to a workspace, or whether the catalog portion can change over time despite openWorldHint.

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?

Two sentences, both load-bearing: the first defines the payload and its fields, the second routes the agent to the consumer of those names. No filler, no restatement of the title, and the most important information leads.

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?

No output schema exists, so the description carries the burden of describing return values, and it does list the per-attribute fields. It is slightly incomplete in not clarifying how current values and the offered catalog are separated in the response, but an agent has enough to call it and interpret the result.

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?

There is a single parameter, profile_id, with 0% schema description coverage, and the description never mentions it or explains which profile it should identify or where to obtain it. With one trivial UUID parameter the omission is not severe, but the description does not compensate for the empty schema coverage.

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?

The description states specifically that this returns the business's current Google attributes plus the full attribute catalog for its primary category, and enumerates the fields of each entry (id, display name, group, value type, allowed values). That is concrete enough to distinguish it from a generic profile fetch, though it never uses an explicit verb like 'retrieve' and never names a sibling for contrast.

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?

It gives real routing guidance: use these attribute names with the 'attributes' field of request_profile_update, which tells the agent this is the read-side companion to a specific mutation tool. It does not state when-not to use it or whether other profile-read tools return overlapping data, so it stops short of a full when/when-not statement.

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