Skip to main content
Glama
Sign In
mcp-lindoai

mcp-lindoai

Official
by lindoai
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

Get Website Team

get_website_team
Read-only

Retrieve the team members assigned to a specific website by providing its ID.

Instructions

Get website team members.

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": {
      "website_id": "<website_id>"
    },
    "name": "get_website_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
website_idYesThe website ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.17
  2. Removedv1.0.16
  3. First observedv1.0.14

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description merely restates the action without adding behavioral context beyond what the annotations provide.

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?

The description is very concise with one sentence, front-loaded with the key action. No unnecessary words, though it could be expanded slightly without losing brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with one parameter and no output schema, the description is minimally adequate but could hint at the return type (e.g., list of team members) to improve completeness.

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?

The single parameter 'website_id' is fully described in the input schema (100% coverage). The description adds no additional meaning or constraints beyond the schema.

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 the verb 'Get' and resource 'website team members', clearly indicating the tool's purpose. However, it does not differentiate from the sibling tool 'get_workspace_team', which has a similar purpose but different scope.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'get_workspace_team'. The description lacks context on prerequisites or conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools