Skip to main content
Glama

Market Brew

Get a Crew account

get_crew
Read-onlyIdempotent

Use this when the user identifies a specific Crew by business name, email, or numeric ID. This resolves the Crew and returns its details, including website summaries, when the linked account is allowed to see it.

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": {
      "crewReference": "<crewReference>"
    },
    "name": "get_crew"
  }
}

Input Schema

NameRequiredDescriptionDefault
crewReferenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / crewReference / anyOf
      Previous value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "exclusiveMinimum": 0,
      -        "maximum": 9007199254740991,
      -        "minimum": -9007199254740991,
      -        "type": "integer"
      -      },
      -      {
      -        "pattern": "^[1-9][0-9]{0,17}$",
      -        "type": "string"
      -      }
      -    ]
      -  },
      -  {
      -    "maxLength": 254,
      -    "minLength": 1,
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  {
      +    "maxLength": 254,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / crewReference / anyOf
      Previous value: -[
      -  {
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]New value: +[
      +  {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  {
      +    "maxLength": 254,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add a genuine behavioral fact beyond the annotations: results include website summaries only when the linked account is permitted to see them, implying permission-gated or partial responses. It says nothing, however, about ambiguous name matches, not-found behavior, or error modes for a resolver that accepts a name string.

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, no filler, and the usage trigger is front-loaded ahead of the return behavior. Every clause carries information an agent needs.

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?

For a single-parameter lookup with no output schema and no nesting, the definition covers trigger, resolution input forms, and the shape of what comes back (details plus optionally visible website summaries). The remaining gap is disambiguation and failure behavior.

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?

With 0% schema description coverage, the schema only shows an anyOf of a positive integer or a 1-254 character string with no explanation, so the description carries the burden and does: it names the three accepted identifier kinds (business name, email, numeric ID). It does not address precedence or what happens if a name matches multiple Crews.

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 pairs a specific verb ("resolves") with a specific resource ("Crew") and enumerates the identifier forms accepted, which lets an agent distinguish this from get_current_crew's implied "own account" scope. It stops short of explicitly naming the sibling it is not.

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 concrete trigger condition: "when the user identifies a specific Crew by business name, email, or numeric ID." It does not state exclusions, such as falling back to get_current_crew when the user means their own account, nor does it name any alternative tool.

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