Skip to main content
Glama

List my codebases

my_library
Read-only

The codebases the signed-in user has bought, newest first: the newest release they can get (release_number), whether they're subscribed to new releases, each codebase's git URL, and whether they can still add a subscription to updates without buying it again (can_add_updates, until add_updates_until, at the listing's add_updates_url). For a listing sold in plans, plan is the one they have (none for its base plan), clone_urls has the git URL of each repository they have (its own, and each of their plans' with code of its own), and upgrade_prices says what upgrading to each plan above theirs costs them, at the plan's purchase_url.

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": {
      "context": "<context>"
    },
    "name": "my_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNoThe maximum number of records to return
filterNoA filter to apply to the query: either a condition {"field": ..., "operator": ..., "value": ...} or an {"and": [...]} / {"or": [...]} group of conditions and groups (nestable). Operators: eq, greater_than, greater_than_or_equal, in, is_distinct_from, is_nil, is_not_distinct_from, less_than, less_than_or_equal, not_eq. For 'is_nil' the value is true or false; for 'in' the value is an array. Fields: id, purchased_release_number, subscribed_until, updates_included, contact_shared_at, plan_id, user_id, listing_id, release_number, clone_urls, upgrade_prices, subscribed?, add_updates_until, can_add_updates?.
offsetNoThe number of records to skip
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as "the user" or "a buyer".
result_typeNoThe type of result to returnrun_query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as \"the user\" or \"a buyer\".",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "context"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / filter / description
      Previous value: -"A filter to apply to the query: either a condition {\"field\": ..., \"operator\": ..., \"value\": ...} or an {\"and\": [...]} / {\"or\": [...]} group of conditions and groups (nestable). Operators: eq, greater_than, greater_than_or_equal, in, is_distinct_from, is_nil, is_not_distinct_from, less_than, less_than_or_equal, not_eq. For 'is_nil' the value is true or false; for 'in' the value is an array. Fields: id, purchased_release_number, subscribed_until, updates_included, contact_shared_at, plan_id, user_id, listing_id, release_number, subscribed?, add_updates_until, can_add_updates?."New value: +"A filter to apply to the query: either a condition {\"field\": ..., \"operator\": ..., \"value\": ...} or an {\"and\": [...]} / {\"or\": [...]} group of conditions and groups (nestable). Operators: eq, greater_than, greater_than_or_equal, in, is_distinct_from, is_nil, is_not_distinct_from, less_than, less_than_or_equal, not_eq. For 'is_nil' the value is true or false; for 'in' the value is an array. Fields: id, purchased_release_number, subscribed_until, updates_included, contact_shared_at, plan_id, user_id, listing_id, release_number, clone_urls, upgrade_prices, subscribed?, add_updates_until, can_add_updates?."
    • changedInput schema / properties / result_type / oneOf
      Previous value: -[
      -  {
      -    "description": "Run the query returning the matching records (up to `limit`), or return a count of results, or check if any results exist",
      -    "enum": [
      -      "run_query",
      -      "count",
      -      "exists"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "properties": {
      -      "aggregate": {
      -        "description": "The aggregate function to use",
      -        "enum": [
      -          "max",
      -          "min",
      -          "sum",
      -          "avg",
      -          "count"
      -        ],
      -        "type": "string"
      -      },
      -      "field": {
      -        "description": "The field to aggregate",
      -        "enum": [
      -          "id",
      -          "purchased_release_number",
      -          "subscribed_until",
      -          "updates_included",
      -          "contact_shared_at",
      -          "plan_id",
      -          "user_id",
      -          "listing_id",
      -          "release_number",
      -          "subscribed?",
      -          "add_updates_until",
      -          "can_add_updates?"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "aggregate",
      -      "field"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "description": "Run the query returning the matching records (up to `limit`), or return a count of results, or check if any results exist",
      +    "enum": [
      +      "run_query",
      +      "count",
      +      "exists"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "properties": {
      +      "aggregate": {
      +        "description": "The aggregate function to use",
      +        "enum": [
      +          "max",
      +          "min",
      +          "sum",
      +          "avg",
      +          "count"
      +        ],
      +        "type": "string"
      +      },
      +      "field": {
      +        "description": "The field to aggregate",
      +        "enum": [
      +          "id",
      +          "purchased_release_number",
      +          "subscribed_until",
      +          "updates_included",
      +          "contact_shared_at",
      +          "plan_id",
      +          "user_id",
      +          "listing_id",
      +          "release_number",
      +          "clone_urls",
      +          "upgrade_prices",
      +          "subscribed?",
      +          "add_updates_until",
      +          "can_add_updates?"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "aggregate",
      +      "field"
      +    ],
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / sort / items / properties / field / enum
      Previous value: -[
      -  "id",
      -  "purchased_release_number",
      -  "subscribed_until",
      -  "updates_included",
      -  "contact_shared_at",
      -  "plan_id",
      -  "user_id",
      -  "listing_id",
      -  "subscribed?",
      -  "add_updates_until",
      -  "can_add_updates?",
      -  "release_number"
      -]New value: +[
      +  "id",
      +  "purchased_release_number",
      +  "subscribed_until",
      +  "updates_included",
      +  "contact_shared_at",
      +  "plan_id",
      +  "user_id",
      +  "listing_id",
      +  "clone_urls",
      +  "upgrade_prices",
      +  "subscribed?",
      +  "add_updates_until",
      +  "can_add_updates?",
      +  "release_number"
      +]
  3. Changed3 schema fields changed
    • changedInput schema / properties / filter / description
      Previous value: -"A filter to apply to the query: either a condition {\"field\": ..., \"operator\": ..., \"value\": ...} or an {\"and\": [...]} / {\"or\": [...]} group of conditions and groups (nestable). Operators: eq, greater_than, greater_than_or_equal, in, is_distinct_from, is_nil, is_not_distinct_from, less_than, less_than_or_equal, not_eq. For 'is_nil' the value is true or false; for 'in' the value is an array. Fields: id, purchased_release_number, subscribed_until, updates_included, contact_shared_at, user_id, listing_id, release_number, subscribed?, add_updates_until, can_add_updates?."New value: +"A filter to apply to the query: either a condition {\"field\": ..., \"operator\": ..., \"value\": ...} or an {\"and\": [...]} / {\"or\": [...]} group of conditions and groups (nestable). Operators: eq, greater_than, greater_than_or_equal, in, is_distinct_from, is_nil, is_not_distinct_from, less_than, less_than_or_equal, not_eq. For 'is_nil' the value is true or false; for 'in' the value is an array. Fields: id, purchased_release_number, subscribed_until, updates_included, contact_shared_at, plan_id, user_id, listing_id, release_number, subscribed?, add_updates_until, can_add_updates?."
    • changedInput schema / properties / result_type / oneOf
      Previous value: -[
      -  {
      -    "description": "Run the query returning the matching records (up to `limit`), or return a count of results, or check if any results exist",
      -    "enum": [
      -      "run_query",
      -      "count",
      -      "exists"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "properties": {
      -      "aggregate": {
      -        "description": "The aggregate function to use",
      -        "enum": [
      -          "max",
      -          "min",
      -          "sum",
      -          "avg",
      -          "count"
      -        ],
      -        "type": "string"
      -      },
      -      "field": {
      -        "description": "The field to aggregate",
      -        "enum": [
      -          "id",
      -          "purchased_release_number",
      -          "subscribed_until",
      -          "updates_included",
      -          "contact_shared_at",
      -          "user_id",
      -          "listing_id",
      -          "release_number",
      -          "subscribed?",
      -          "add_updates_until",
      -          "can_add_updates?"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "aggregate",
      -      "field"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "description": "Run the query returning the matching records (up to `limit`), or return a count of results, or check if any results exist",
      +    "enum": [
      +      "run_query",
      +      "count",
      +      "exists"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "properties": {
      +      "aggregate": {
      +        "description": "The aggregate function to use",
      +        "enum": [
      +          "max",
      +          "min",
      +          "sum",
      +          "avg",
      +          "count"
      +        ],
      +        "type": "string"
      +      },
      +      "field": {
      +        "description": "The field to aggregate",
      +        "enum": [
      +          "id",
      +          "purchased_release_number",
      +          "subscribed_until",
      +          "updates_included",
      +          "contact_shared_at",
      +          "plan_id",
      +          "user_id",
      +          "listing_id",
      +          "release_number",
      +          "subscribed?",
      +          "add_updates_until",
      +          "can_add_updates?"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "aggregate",
      +      "field"
      +    ],
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / sort / items / properties / field / enum
      Previous value: -[
      -  "id",
      -  "purchased_release_number",
      -  "subscribed_until",
      -  "updates_included",
      -  "contact_shared_at",
      -  "user_id",
      -  "listing_id",
      -  "subscribed?",
      -  "add_updates_until",
      -  "can_add_updates?",
      -  "release_number"
      -]New value: +[
      +  "id",
      +  "purchased_release_number",
      +  "subscribed_until",
      +  "updates_included",
      +  "contact_shared_at",
      +  "plan_id",
      +  "user_id",
      +  "listing_id",
      +  "subscribed?",
      +  "add_updates_until",
      +  "can_add_updates?",
      +  "release_number"
      +]
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnly and closed-world; the description adds real behavioral detail beyond that: results are scoped to the signed-in user, default ordering is newest first, and fields are conditional on purchase type (plan-based listings populate plan/clone_urls/upgrade_prices). It does not mention pagination defaults or that the tool can also count/exists rather than list, which the schema handles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, which is good. But the second half degenerates into deeply nested parentheticals ("`can_add_updates`, until `add_updates_until`, at the listing's `add_updates_url`") that are hard to parse and read more like field documentation than tool guidance.

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 return-value explanation and does so thoroughly, covering release_number, subscription state, git URLs, plan/upgrade pricing and the add-updates URL. Given six parameters documented at 83% coverage, an agent has enough to call it correctly; only pagination and aggregate-mode guidance are absent.

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 coverage is 83%, so the schema already documents sort, filter, limit, offset and result_type. The description adds only indirectly, via "newest first" hinting at the default sort, and says nothing about filterable fields or the count/exists result modes. Baseline 3 applies when the schema carries the parameter burden.

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?

Opening clause names the resource and scope precisely: "The codebases the signed-in user has bought, newest first." That distinguishes it from search_codebases and my_subscriptions by ownership rather than query. It is phrased as a noun phrase rather than a verb+resource action, and most of the remaining text is about returned fields rather than purpose.

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 implied by "bought" (owned library vs. search) and by the subscription/clone-URL field descriptions, which suggest post-purchase management. However, no sibling is named and no when-not-to-use condition is stated. The agent must infer that it should use search_codebases for discovery and this tool for owned codebases.

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