Skip to main content
Glama

Take My Repo

Get one project or model

get_resource
Read-only

Facts about one repository, model, demo or dataset: description, license (or that none is declared), topics, popularity, last update, source link, and Take My Repo's review count and average rating.

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": {
      "uid": "<uid>"
    },
    "name": "get_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesTake My Repo id: gh/{owner}/{repo} for GitHub, or hf/{model|space|dataset}/{id} for Hugging Face.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value by enumerating what comes back (license state, popularity, last update, review aggregates) and by noting the explicit "or that none is declared" edge case for licenses, but it says nothing about behavior for a missing/unknown uid or about coverage gaps across the four entity types. That is useful but thin beyond what the annotations supply.

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?

One front-loaded sentence with no filler, and the field enumeration is well placed after the core statement of purpose. The colon-and-list construction is dense but readable; it stops just short of being a run-on.

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?

With no output schema, the description must carry return-value burden and does so reasonably by naming the returned facts and the review count/average. It is still incomplete for a lookup tool: nothing about not-found behavior, whether entity types differ in returned fields, or what "popularity" actually measures.

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 100%: the uid property already documents the gh/{owner}/{repo} and hf/{model|space|dataset}/{id} formats with examples. The description adds no further parameter meaning, so the baseline 3 applies.

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?

"Facts about one repository, model, demo or dataset" names both the resource and its singular scope, and the field list that follows makes it unambiguous this is a detail lookup rather than a search or review listing. It separates cleanly from siblings like search and get_reviews, though it never names an alternative explicitly.

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: "one" plus a required uid signals 'call this when you already have an identifier,' but there is no explicit when-to-use, when-not, or pointer to alternatives such as search or get_install_plan. An agent must infer the routing rule from the parameter shape.

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