Skip to main content
Glama

Get Profile Guard snapshot

get_profile_guard_snapshot
Read-onlyIdempotent

Profile Guard's protected values for a profile (the last approved value of each watched field) plus changes detected on Google that are still waiting for a decision. Use request_profile_change_decision to accept or undo a pending change.

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

Input Schema

NameRequiredDescriptionDefault
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and closed-world scope, so safety is covered structurally. Beyond that, the description adds real semantic context about what the read contains (approved baseline values versus undecided changes), which matters since there is no output schema to describe the payload.

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, the payload definition is front-loaded, and the second sentence exists solely to route the agent to the decision tool. Nothing is redundant or padded.

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?

With no output schema, the description carries the burden of explaining the return payload and does so at a high level. It stops short of describing shape, size, or what happens when no pending changes exist, which leaves a small gap for a snapshot-style read.

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?

Schema description coverage is 0%, but the single parameter is profile_id with a uuid format and its meaning is transparent from the name and from the description's 'for a profile' phrasing. The description adds no format, scope, or access constraints beyond that, so it neither compensates further nor misleads.

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 description names a specific resource (Profile Guard's protected values for one profile) and enumerates the two things returned: the last approved value of each watched field and Google-detected changes awaiting a decision. That is far more precise than a restatement of the name, and it lets an agent tell this apart from a change-list or attribute-list tool.

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 a clear follow-up route: pending changes should be acted on via request_profile_change_decision. What it does not state is when to prefer this snapshot over sibling surfaces like list_profile_changes or get_profile_attributes, so the routing is helpful but not fully exclusive.

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