Skip to main content
Glama

Premiss connected workspace

get_profile
Read-onlyIdempotent

Read the stable identity and workspace selected for this connection, plus the next step to take with the user. Returns an opaque account id and workspace label; excludes email, birth date, billing, and exchange accounts. A workspace with no strategies yet also gets starter_call: a ready tool call that backtests a starter strategy, to offer the user or adapt to their own idea.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idYes
app_urlYes
next_stepYes
workspaceYes
permissionsYes
starter_callYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
      +  "__schema0": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "number"
      +      },
      +      {
      +        "type": "boolean"
      +      },
      +      {
      +        "type": "null"
      +      },
      +      {
      +        "items": {
      +          "$ref": "#/$defs/__schema0"
      +        },
      +        "type": "array"
      +      },
      +      {
      +        "additionalProperties": {
      +          "$ref": "#/$defs/__schema0"
      +        },
      +        "propertyNames": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      }
      +    ]
      +  }
      +}
    • addedOutput schema / properties / next_step
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / starter_call
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "arguments": {
      +          "additionalProperties": {
      +            "$ref": "#/$defs/__schema0"
      +          },
      +          "propertyNames": {
      +            "type": "string"
      +          },
      +          "type": "object"
      +        },
      +        "tool": {
      +          "enum": [
      +            "test_strategy",
      +            "create_strategy"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "tool",
      +        "arguments"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "workspace",
      -  "permissions",
      -  "app_url"
      -]New value: +[
      +  "id",
      +  "workspace",
      +  "permissions",
      +  "app_url",
      +  "next_step",
      +  "starter_call"
      +]
  2. 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, non-destructive, closed-world, so safety is covered; the description adds genuinely new behavior — the precise privacy exclusions and the conditional starter_call that only appears for workspaces with no strategies. It stops short of describing error or empty-connection outcomes, which keeps it from a 5.

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?

Two tight sentences, front-loaded with what is returned and followed by scope limits and the conditional starter_call. The second sentence is dense and packs two ideas (no-strategies condition and how to use starter_call), which slightly slows parsing.

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?

With an output schema present, return-value detail is unnecessary, and the zero-param schema needs no explanation. The description nonetheless covers identity scope, privacy exclusions, and a conditional field the agent should act on — enough for correct invocation.

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. The description does not waste words restating the empty schema.

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 verb (read) and resource (stable identity and workspace for this connection) and immediately bounds the returned data by listing exclusions (email, birth date, billing, exchange accounts). This clearly separates it from siblings like get_capabilities or get_strategy, which cover different resources.

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?

Usage is only implied: 'the next step to take with the user' and the starter_call hint suggest an onboarding/first-contact moment, but the description never states explicitly when to call this versus get_capabilities or describe_market, nor any preconditions. An agent can infer a session-start role but must guess the boundaries.

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